From: Jason Wang <jasowang@redhat.com>
To: "Eugenio Pérez" <eperezma@redhat.com>, qemu-devel@nongnu.org
Cc: Lei Yang <leiyang@redhat.com>, "Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [PATCH v2 1/2] vdpa: Skip the maps not in the iova tree
Date: Fri, 5 Aug 2022 10:28:53 +0800 [thread overview]
Message-ID: <907485db-d53a-9e32-e447-39d67ce8c9a5@redhat.com> (raw)
In-Reply-To: <20220804155443.671136-2-eperezma@redhat.com>
在 2022/8/4 23:54, Eugenio Pérez 写道:
> Next patch will skip the registering of dma maps that the vdpa device
> rejects in the iova tree. We need to consider that here or we cause a
> SIGSEGV accessing result.
>
> Reported-by: Lei Yang <leiyang@redhat.com>
> Signed-off-by: Eugenio Pérez <eperezma@redhat.com>
Acked-by: Jason Wang <jasowang@redhat.com>
> ---
> hw/virtio/vhost-vdpa.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/hw/virtio/vhost-vdpa.c b/hw/virtio/vhost-vdpa.c
> index 3ff9ce3501..983d3697b0 100644
> --- a/hw/virtio/vhost-vdpa.c
> +++ b/hw/virtio/vhost-vdpa.c
> @@ -289,6 +289,10 @@ static void vhost_vdpa_listener_region_del(MemoryListener *listener,
> };
>
> result = vhost_iova_tree_find_iova(v->iova_tree, &mem_region);
> + if (!result) {
> + /* The memory listener map wasn't mapped */
> + return;
> + }
> iova = result->iova;
> vhost_iova_tree_remove(v->iova_tree, result);
> }
next prev parent reply other threads:[~2022-08-05 2:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-04 15:54 [PATCH v2 0/2] vdpa: do not save failed dma maps in SVQ iova tree Eugenio Pérez
2022-08-04 15:54 ` [PATCH v2 1/2] vdpa: Skip the maps not in the " Eugenio Pérez
2022-08-05 2:28 ` Jason Wang [this message]
2022-08-04 15:54 ` [PATCH v2 2/2] vdpa: do not save failed dma maps in SVQ " Eugenio Pérez
2022-08-05 2:36 ` Jason Wang
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=907485db-d53a-9e32-e447-39d67ce8c9a5@redhat.com \
--to=jasowang@redhat.com \
--cc=eperezma@redhat.com \
--cc=leiyang@redhat.com \
--cc=mst@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).