All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "Kevin Wolf" <kwolf@redhat.com>,
	"Marc Marí" <marc.mari.barcelo@gmail.com>,
	"Fam Zheng" <famz@redhat.com>,
	"Stefan Hajnoczi" <stefanha@gmail.com>,
	"Jason Wang" <jasowang@redhat.com>,
	qemu-devel <qemu-devel@nongnu.org>,
	"Stefan Hajnoczi" <stefanha@redhat.com>
Subject: Re: [Qemu-devel] [PATCH RFC for-2.2] virtio-blk: force 1st s/g to match header
Date: Sun, 30 Nov 2014 18:43:05 +0200	[thread overview]
Message-ID: <20141130164305.GA10852@redhat.com> (raw)
In-Reply-To: <CAFEAcA88Sg05F5kr0QJZ=6RwG1XKVnddSUKoLnDZKCBdLGGs8g@mail.gmail.com>

On Fri, Nov 28, 2014 at 04:14:35PM +0000, Peter Maydell wrote:
> On 28 November 2014 at 11:43, Stefan Hajnoczi <stefanha@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 or it needs to expect QEMU to refuse (in this case
> > exit(1), which is not very graceful).
> >
> > The quick fix is to skip the 2-descriptor layout tests and re-enable
> > them once virtio-blk actually supports ANY_LAYOUT.  Any objections?
> 
> So what do we want to do with this for 2.2? We have I think
> two choices:
>  (1) say that this isn't causing problems in practice, and defer all
>  this to 2.3
>  (2) add something like this patch plus fix the 'make check' tests
>  (but turning "maybe something misbehaves" into "qemu definitely
>  blows up and exits" doesn't seem like a great improvement to me)
> 
> I started looking at virtio-blk initially because I wasn't sure
> if we should fix the virtio-net issue in the core virtio code.
> But since we've decided not to do that, whether virtio-blk's
> problems are release-blockers or not is something that we can
> decide on their own merits.
> 
> My current thought is that we don't need to address this for 2.2;
> is there something I'm missing that means we shouldn't defer to 2.3?
> 
> thanks
> -- PMM

The result of this is host mapping leak.
What effect does this have? Can this DOS host?
If not, I agree.

  reply	other threads:[~2014-11-30 16:43 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-27 16:33 [Qemu-devel] [PATCH RFC for-2.2] virtio-blk: force 1st s/g to match header Michael S. Tsirkin
2014-11-27 19:21 ` Stefan Hajnoczi
2014-11-27 21:13   ` Michael S. Tsirkin
2014-11-28  1:16     ` Fam Zheng
2014-11-28  7:05       ` Jason Wang
2014-11-28 11:43         ` Stefan Hajnoczi
2014-11-28 14:05           ` Marc Marí
2014-11-28 16:14           ` Peter Maydell
2014-11-30 16:43             ` Michael S. Tsirkin [this message]
2014-12-01 12:07               ` Peter Maydell
2014-12-01 12:18                 ` Michael S. Tsirkin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20141130164305.GA10852@redhat.com \
    --to=mst@redhat.com \
    --cc=famz@redhat.com \
    --cc=jasowang@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=marc.mari.barcelo@gmail.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@gmail.com \
    --cc=stefanha@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.