qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jason Wang <jasowang@redhat.com>
To: "Eugenio Pérez" <eperezma@redhat.com>, qemu-devel@nongnu.org
Cc: Lei Yang <leiyang@redhat.com>,
	Laurent Vivier <lvivier@redhat.com>, Cindy Lu <lulu@redhat.com>,
	Peter Xu <peterx@redhat.com>,
	"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [PATCH 6/7] vhost: Always store new kick fd on vhost_svq_set_svq_kick_fd
Date: Tue, 23 Aug 2022 14:38:33 +0800	[thread overview]
Message-ID: <9505e7a3-b42b-ec94-7670-66bce3919394@redhat.com> (raw)
In-Reply-To: <20220819165357.3591965-7-eperezma@redhat.com>


在 2022/8/20 00:53, Eugenio Pérez 写道:
> We can unbind twice a file descriptor if we call twice
> vhost_svq_set_svq_kick_fd because of this. Since it comes from vhost and
> not from SVQ, that file descriptor could be a different thing that
> guest's vhost notifier.
>
> Likewise, it can happens the same if a guest start and stop the device
> multiple times.
>
> Reported-by: Lei Yang <leiyang@redhat.com>
> Fixes: dff4426fa6 ("vhost: Add Shadow VirtQueue kick forwarding capabilities")
> Signed-off-by: Eugenio Pérez <eperezma@redhat.com>
> ---


Acked-by: Jason Wang <jasowang@redhat.com>


>   hw/virtio/vhost-shadow-virtqueue.c | 4 ++--
>   1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/hw/virtio/vhost-shadow-virtqueue.c b/hw/virtio/vhost-shadow-virtqueue.c
> index e4956728dd..82a784d250 100644
> --- a/hw/virtio/vhost-shadow-virtqueue.c
> +++ b/hw/virtio/vhost-shadow-virtqueue.c
> @@ -602,13 +602,13 @@ void vhost_svq_set_svq_kick_fd(VhostShadowVirtqueue *svq, int svq_kick_fd)
>           event_notifier_set_handler(svq_kick, NULL);
>       }
>   
> +    event_notifier_init_fd(svq_kick, svq_kick_fd);
>       /*
>        * event_notifier_set_handler already checks for guest's notifications if
>        * they arrive at the new file descriptor in the switch, so there is no
>        * need to explicitly check for them.
>        */
>       if (poll_start) {
> -        event_notifier_init_fd(svq_kick, svq_kick_fd);
>           event_notifier_set(svq_kick);
>           event_notifier_set_handler(svq_kick, vhost_handle_guest_kick_notifier);
>       }
> @@ -655,7 +655,7 @@ void vhost_svq_start(VhostShadowVirtqueue *svq, VirtIODevice *vdev,
>    */
>   void vhost_svq_stop(VhostShadowVirtqueue *svq)
>   {
> -    event_notifier_set_handler(&svq->svq_kick, NULL);
> +    vhost_svq_set_svq_kick_fd(svq, VHOST_FILE_UNBIND);
>       g_autofree VirtQueueElement *next_avail_elem = NULL;
>   
>       if (!svq->vq) {



  reply	other threads:[~2022-08-23  6:43 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-19 16:53 [PATCH 0/7] vDPA shadow virtqueue iova tree fixes Eugenio Pérez
2022-08-19 16:53 ` [PATCH 1/7] vdpa: Skip the maps not in the iova tree Eugenio Pérez
2022-08-19 16:53 ` [PATCH 2/7] vdpa: do not save failed dma maps in SVQ " Eugenio Pérez
2022-08-19 16:53 ` [PATCH 3/7] util: make a copy of iova_tree_remove_parameter Eugenio Pérez
2022-08-23  6:18   ` Jason Wang
2022-08-23  9:55     ` Eugenio Perez Martin
2022-08-19 16:53 ` [PATCH 4/7] vdpa: Remove SVQ vring from iova_tree at shutdown Eugenio Pérez
2022-08-23  6:25   ` Jason Wang
2022-08-23 11:29     ` Eugenio Perez Martin
2022-08-19 16:53 ` [PATCH 5/7] vdpa: Make SVQ vring unmapping return void Eugenio Pérez
2022-08-23  6:33   ` Jason Wang
2022-08-19 16:53 ` [PATCH 6/7] vhost: Always store new kick fd on vhost_svq_set_svq_kick_fd Eugenio Pérez
2022-08-23  6:38   ` Jason Wang [this message]
2022-08-19 16:53 ` [PATCH 7/7] vdpa: Use ring hwaddr at vhost_vdpa_svq_unmap_ring Eugenio Pérez
2022-08-23  6:40   ` Jason Wang
2022-08-23 11:32     ` Eugenio Perez Martin

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=9505e7a3-b42b-ec94-7670-66bce3919394@redhat.com \
    --to=jasowang@redhat.com \
    --cc=eperezma@redhat.com \
    --cc=leiyang@redhat.com \
    --cc=lulu@redhat.com \
    --cc=lvivier@redhat.com \
    --cc=mst@redhat.com \
    --cc=peterx@redhat.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 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).