On 30 November 2014 at 16:43, Michael S. Tsirkin m...@redhat.com wrote:
The result of this is host mapping leak.
What effect does this have? Can this DOS host?
I don't think we can DOS the host here.
If Xen, we crash (but you can't use virtio-blk with Xen anyway)
Otherwise, if you managed to
On Mon, Dec 01, 2014 at 12:07:07PM +, Peter Maydell wrote:
On 30 November 2014 at 16:43, Michael S. Tsirkin m...@redhat.com wrote:
The result of this is host mapping leak.
What effect does this have? Can this DOS host?
I don't think we can DOS the host here.
If Xen, we crash (but
On Fri, Nov 28, 2014 at 04:14:35PM +, Peter Maydell wrote:
On 28 November 2014 at 11:43, Stefan Hajnoczi stefa...@gmail.com wrote:
Right, the test case explicitly tests different descriptor layouts,
even though virtio-blk-pci does not set the ANY_LAYOUT feature bit.
Either the test
On Fri, Nov 28, 2014 at 7:05 AM, Jason Wang jasow...@redhat.com wrote:
On Fri, Nov 28, 2014 at 9:16 AM, Fam Zheng f...@redhat.com wrote:
On Thu, 11/27 23:13, Michael S. Tsirkin wrote:
On Thu, Nov 27, 2014 at 07:21:35PM +, Stefan Hajnoczi wrote:
On Thu, Nov 27, 2014 at 4:33 PM,
El Fri, 28 Nov 2014 11:43:59 +
Stefan Hajnoczi stefa...@gmail.com escribió:
On Fri, Nov 28, 2014 at 7:05 AM, Jason Wang jasow...@redhat.com
wrote:
On Fri, Nov 28, 2014 at 9:16 AM, Fam Zheng f...@redhat.com wrote:
On Thu, 11/27 23:13, Michael S. Tsirkin wrote:
On Thu, Nov 27,
On 28 November 2014 at 11:43, Stefan Hajnoczi stefa...@gmail.com wrote:
Right, the test case explicitly tests different descriptor layouts,
even though virtio-blk-pci does not set the ANY_LAYOUT feature bit.
Either the test case needs to check ANY_LAYOUT before using the
2-descriptor layout
We leak cpu mappings when 1st s/g is not exactly the
header. As we don't set ANY_LAYOUT, we can at this point
simply assert the correct length.
This will have to be fixed once ANY_LAYOUT is set.
Signed-off-by: Michael S. Tsirkin m...@redhat.com
---
Untested: posting for early feedback.
On Thu, Nov 27, 2014 at 4:33 PM, Michael S. Tsirkin m...@redhat.com wrote:
We leak cpu mappings when 1st s/g is not exactly the
header. As we don't set ANY_LAYOUT, we can at this point
simply assert the correct length.
This will have to be fixed once ANY_LAYOUT is set.
Signed-off-by:
On Thu, Nov 27, 2014 at 07:21:35PM +, Stefan Hajnoczi wrote:
On Thu, Nov 27, 2014 at 4:33 PM, Michael S. Tsirkin m...@redhat.com wrote:
We leak cpu mappings when 1st s/g is not exactly the
header. As we don't set ANY_LAYOUT, we can at this point
simply assert the correct length.
On Thu, 11/27 23:13, Michael S. Tsirkin wrote:
On Thu, Nov 27, 2014 at 07:21:35PM +, Stefan Hajnoczi wrote:
On Thu, Nov 27, 2014 at 4:33 PM, Michael S. Tsirkin m...@redhat.com wrote:
We leak cpu mappings when 1st s/g is not exactly the
header. As we don't set ANY_LAYOUT, we can at
On Fri, Nov 28, 2014 at 9:16 AM, Fam Zheng f...@redhat.com wrote:
On Thu, 11/27 23:13, Michael S. Tsirkin wrote:
On Thu, Nov 27, 2014 at 07:21:35PM +, Stefan Hajnoczi wrote:
On Thu, Nov 27, 2014 at 4:33 PM, Michael S. Tsirkin
m...@redhat.com wrote:
We leak cpu mappings when 1st
11 matches
Mail list logo
