qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: Jason Wang <jasowang@redhat.com>,
	qemu-devel@nongnu.org, qemu-stable <qemu-stable@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH for 2.3 V2] virtio-net: validate backend queue numbers against bus limitation
Date: Mon, 23 Mar 2015 14:51:51 +0100	[thread overview]
Message-ID: <20150323145127-mutt-send-email-mst@redhat.com> (raw)
In-Reply-To: <20150323132028.GG9268@stefanha-thinkpad.redhat.com>

On Mon, Mar 23, 2015 at 01:20:28PM +0000, Stefan Hajnoczi wrote:
> On Fri, Mar 20, 2015 at 02:07:50PM +0800, Jason Wang wrote:
> > We don't validate the backend queue numbers against bus limitation,
> > this will easily crash qemu if it exceeds the limitation which will
> > hit the abort() in virtio_del_queue(). An example is trying to
> > starting a virtio-net device with 256 queues. E.g:
> > 
> > ./qemu-system-x86_64 -netdev tap,id=hn0,queues=256 -device
> > virtio-net-pci,netdev=hn0
> > 
> > Fixing this by doing the validation and fail early.
> > 
> > Cc: Michael S. Tsirkin <mst@redhat.com>
> > Cc: qemu-stable <qemu-stable@nongnu.org>
> > Signed-off-by: Jason Wang <jasowang@redhat.com>
> > ---
> > Changes from V1:
> > Tweak the commit log.
> > ---
> >  hw/net/virtio-net.c | 7 +++++++
> >  1 file changed, 7 insertions(+)
> > 
> > diff --git a/hw/net/virtio-net.c b/hw/net/virtio-net.c
> > index 27adcc5..59f76bc 100644
> > --- a/hw/net/virtio-net.c
> > +++ b/hw/net/virtio-net.c
> > @@ -1588,6 +1588,13 @@ static void virtio_net_device_realize(DeviceState *dev, Error **errp)
> >      virtio_init(vdev, "virtio-net", VIRTIO_ID_NET, n->config_size);
> >  
> >      n->max_queues = MAX(n->nic_conf.peers.queues, 1);
> > +    if (n->max_queues * 2 + 1 > VIRTIO_PCI_QUEUE_MAX) {
> > +        error_setg(errp, "Invalid number of queues (= %" PRIu32 "), "
> > +                   "must be a postive integer less than %d.",
> > +                   n->max_queues, (VIRTIO_PCI_QUEUE_MAX - 1) / 2);
> > +        virtio_cleanup(vdev);
> > +        return;
> > +    }
> 
> If VIRTIO_PCI_QUEUE_MAX is really PCI-only then this is a layering
> violation.  Virtio devices should not assume a particular transport
> (PCI, CCW, etc).
> 
> Either the constant should be renamed if it truly applies to all
> transports, or there should be a virtio_get_max_queues() function that
> lets the transport pick a value.
> 
> That said, virtio-scsi.c already checks VIRTIO_PCI_QUEUE_MAX so maybe
> this patch is fine and a cleanup should be written later:
> 
> Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>

Yes, we need to rename this constant, no problem here.

      reply	other threads:[~2015-03-23 13:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-20  6:07 [Qemu-devel] [PATCH for 2.3 V2] virtio-net: validate backend queue numbers against bus limitation Jason Wang
2015-03-23 13:20 ` Stefan Hajnoczi
2015-03-23 13:51   ` Michael S. Tsirkin [this message]

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=20150323145127-mutt-send-email-mst@redhat.com \
    --to=mst@redhat.com \
    --cc=jasowang@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-stable@nongnu.org \
    --cc=stefanha@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).