From: Halil Pasic <pasic@linux.ibm.com>
To: linux-s390@vger.kernel.org, kvm@vger.kernel.org
Subject: Re: [PATCH 1/1] s390/virtio: handle find on invalid queue gracefully
Date: Mon, 07 Jan 2019 15:33:50 +0000 [thread overview]
Message-ID: <20190107163350.3f220041@oc2783563651> (raw)
In-Reply-To: <20190107160632.06b6f624.cohuck@redhat.com>
On Mon, 7 Jan 2019 16:06:32 +0100
Cornelia Huck <cohuck@redhat.com> wrote:
> On Mon, 7 Jan 2019 13:31:46 +0100
> Halil Pasic <pasic@linux.ibm.com> wrote:
>
> > A queue with a capacity of zero is clearly not a valid virtio queue.
> > Some emulators report zero queue size if queried with an invalid queue
> > index. Instead of crashing in this case let us just return -EINVAL. To
>
> s/-EINVAL/-ENOENT/
>
So I did forget something, again. :/ Thanks for spotting it!
> > make that work properly, let us fix the notifier cleanup logic as well.
> >
> > Signed-off-by: Halil Pasic <pasic@linux.ibm.com>
> > ---
> > This patch is motivated by commit 86a5597 "virtio-balloon:
> > VIRTIO_BALLOON_F_FREE_PAGE_HINT" (Wei Wang, 2018-08-27) which triggered
> > the described scenario. The emulator in question is the current QEMU.
> > The problem we run into is the underflow in the following loop
> > in __vring_new_virtqueue():
> > for (i = 0; i < vring.num-1; i++)
> > vq->vring.desc[i].next = cpu_to_virtio16(vdev, i + 1)
> > Namely vring.num is an unsigned int.
> >
> > RFC --> v1:
> > * Change error code from -EINVAL to -ENOENT, so we are in line with the
> > other transports.
> > * Push down the detection of the error into virtio_ccw_read_vq_conf().
> > ---
> > drivers/s390/virtio/virtio_ccw.c | 4 +++-
> > 1 file changed, 3 insertions(+), 1 deletion(-)
>
> Thanks, applied.
>
Thanks!
Halil
parent reply other threads:[~2019-01-07 15:33 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20190107160632.06b6f624.cohuck@redhat.com>]
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=20190107163350.3f220041@oc2783563651 \
--to=pasic@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
/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