From: "Michael S. Tsirkin" <mst@redhat.com>
To: Li Qiang <liq3ea@gmail.com>
Cc: Li Qiang <liq3ea@163.com>,
Qemu Developers <qemu-devel@nongnu.org>,
David Hildenbrand <david@redhat.com>
Subject: Re: [PATCH v2] virtio-mem: detach the element from the virtqueue when error occurs
Date: Tue, 8 Sep 2020 10:10:44 -0400 [thread overview]
Message-ID: <20200908101025-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <CAKXe6SLt8r3bm0bGiGQ5sPoz-8xWrZkpnRFa1GEaT5_iRO1+Rg@mail.gmail.com>
For some reason I didn't receive the original email.
Sorry.
Queued now.
On Mon, Sep 07, 2020 at 09:36:40AM +0800, Li Qiang wrote:
> Ping!
>
> Li Qiang <liq3ea@gmail.com> 于2020年8月28日周五 上午9:21写道:
> >
> > Kindly ping.
> >
> > Li Qiang <liq3ea@163.com> 于2020年8月16日周日 下午10:23写道:
> > >
> > > If error occurs while processing the virtio request we should call
> > > 'virtqueue_detach_element' to detach the element from the virtqueue
> > > before free the elem.
> > >
> > > Signed-off-by: Li Qiang <liq3ea@163.com>
> > > ---
> > > Change since v1:
> > > Change the subject
> > > Avoid using the goto label
> > >
> > > hw/virtio/virtio-mem.c | 3 +++
> > > 1 file changed, 3 insertions(+)
> > >
> > > diff --git a/hw/virtio/virtio-mem.c b/hw/virtio/virtio-mem.c
> > > index 7740fc613f..e6ffc781b3 100644
> > > --- a/hw/virtio/virtio-mem.c
> > > +++ b/hw/virtio/virtio-mem.c
> > > @@ -318,6 +318,7 @@ static void virtio_mem_handle_request(VirtIODevice *vdev, VirtQueue *vq)
> > > if (iov_to_buf(elem->out_sg, elem->out_num, 0, &req, len) < len) {
> > > virtio_error(vdev, "virtio-mem protocol violation: invalid request"
> > > " size: %d", len);
> > > + virtqueue_detach_element(vq, elem, 0);
> > > g_free(elem);
> > > return;
> > > }
> > > @@ -327,6 +328,7 @@ static void virtio_mem_handle_request(VirtIODevice *vdev, VirtQueue *vq)
> > > virtio_error(vdev, "virtio-mem protocol violation: not enough space"
> > > " for response: %zu",
> > > iov_size(elem->in_sg, elem->in_num));
> > > + virtqueue_detach_element(vq, elem, 0);
> > > g_free(elem);
> > > return;
> > > }
> > > @@ -348,6 +350,7 @@ static void virtio_mem_handle_request(VirtIODevice *vdev, VirtQueue *vq)
> > > default:
> > > virtio_error(vdev, "virtio-mem protocol violation: unknown request"
> > > " type: %d", type);
> > > + virtqueue_detach_element(vq, elem, 0);
> > > g_free(elem);
> > > return;
> > > }
> > > --
> > > 2.17.1
> > >
> > >
>
next prev parent reply other threads:[~2020-09-08 14:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-16 14:22 [PATCH v2] virtio-mem: detach the element from the virtqueue when error occurs Li Qiang
2020-08-17 7:34 ` David Hildenbrand
2020-08-28 1:21 ` Li Qiang
2020-09-07 1:36 ` Li Qiang
2020-09-08 8:55 ` David Hildenbrand
2020-09-08 14:10 ` Michael S. Tsirkin [this message]
2020-09-08 14:46 ` Li Qiang
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=20200908101025-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=david@redhat.com \
--cc=liq3ea@163.com \
--cc=liq3ea@gmail.com \
--cc=qemu-devel@nongnu.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 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.