From: Jason Wang <jasowang@redhat.com>
To: P J P <ppandit@redhat.com>
Cc: Peter Xu <peterx@redhat.com>,
QEMU Developers <qemu-devel@nongnu.org>,
Michael S Tsirkin <mst@redhat.com>,
Prasad Pandit <pjp@fedoraproject.org>
Subject: Re: [PATCH v2 1/2] vhost: release memory_listener object in error path
Date: Wed, 31 May 2023 09:19:50 +0800 [thread overview]
Message-ID: <CACGkMEuKDOR10=gviUtrowxtQtY8QVYdbKSo0MBgnPMTG01gLA@mail.gmail.com> (raw)
In-Reply-To: <20230529114333.31686-2-ppandit@redhat.com>
On Mon, May 29, 2023 at 7:41 PM P J P <ppandit@redhat.com> wrote:
>
> From: Prasad Pandit <pjp@fedoraproject.org>
>
> vhost_dev_start function does not release memory_listener object
> in case of an error. This may crash the guest when vhost is unable
> to set memory table:
>
> stack trace of thread 125653:
> Program terminated with signal SIGSEGV, Segmentation fault
> #0 memory_listener_register (qemu-kvm + 0x6cda0f)
> #1 vhost_dev_start (qemu-kvm + 0x699301)
> #2 vhost_net_start (qemu-kvm + 0x45b03f)
> #3 virtio_net_set_status (qemu-kvm + 0x665672)
> #4 qmp_set_link (qemu-kvm + 0x548fd5)
> #5 net_vhost_user_event (qemu-kvm + 0x552c45)
> #6 tcp_chr_connect (qemu-kvm + 0x88d473)
> #7 tcp_chr_new_client (qemu-kvm + 0x88cf83)
> #8 tcp_chr_accept (qemu-kvm + 0x88b429)
> #9 qio_net_listener_channel_func (qemu-kvm + 0x7ac07c)
> #10 g_main_context_dispatch (libglib-2.0.so.0 + 0x54e2f)
>
> Release memory_listener objects in the error path.
>
> Signed-off-by: Prasad Pandit <pjp@fedoraproject.org>
Cc: qemu-stable@nongnu.org
Acked-by: Jason Wang <jasowang@redhat.com>
Thanks
> ---
> hw/virtio/vhost.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> v2: split a single patch into two. Mention about vhost set mem table failure
> resulting in guest crash.
>
> diff --git a/hw/virtio/vhost.c b/hw/virtio/vhost.c
> index 23da579ce2..6be4a0626a 100644
> --- a/hw/virtio/vhost.c
> +++ b/hw/virtio/vhost.c
> @@ -2004,6 +2004,9 @@ fail_vq:
> }
>
> fail_mem:
> + if (vhost_dev_has_iommu(hdev)) {
> + memory_listener_unregister(&hdev->iommu_listener);
> + }
> fail_features:
> vdev->vhost_started = false;
> hdev->started = false;
> --
> 2.40.1
>
next prev parent reply other threads:[~2023-05-31 1:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-29 11:43 [PATCH v2 0/2] vhost: release memory objects in an error path P J P
2023-05-29 11:43 ` [PATCH v2 1/2] vhost: release memory_listener object in " P J P
2023-05-29 15:06 ` Peter Xu
2023-05-31 1:19 ` Jason Wang [this message]
2023-05-29 11:43 ` [PATCH v2 2/2] vhost: release virtqueue objects " P J P
2023-05-29 15:06 ` Peter Xu
2023-05-31 1:22 ` 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='CACGkMEuKDOR10=gviUtrowxtQtY8QVYdbKSo0MBgnPMTG01gLA@mail.gmail.com' \
--to=jasowang@redhat.com \
--cc=mst@redhat.com \
--cc=peterx@redhat.com \
--cc=pjp@fedoraproject.org \
--cc=ppandit@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).