From: Raphael Norwitz <raphael.s.norwitz@gmail.com>
To: Bobo Du <dubo163@126.com>
Cc: QEMU <qemu-devel@nongnu.org>
Subject: Re: [PATCH] vhost-user-blk.c:fix the qemu-kvm crash in the vhost-user-blk env.
Date: Wed, 20 Jan 2021 12:50:32 -0600 [thread overview]
Message-ID: <CAFubqFtX-vWJ8ajnxVeh9r677Pr1mxvRayj7aOfCAeduWTf-hA@mail.gmail.com> (raw)
In-Reply-To: <20210120035027.51037-1-dubo163@126.com>
Looks good - I just suggest some suggestions for the commit message.
On Wed, Jan 20, 2021 at 8:46 AM Bobo Du <dubo163@126.com> wrote:
>
> In our spdk env, when we restart spdk vhost process, all the spdk
> vhost dev will be reconnected,if the vhost_user_blk_device_realize
> failed in the reconnect code goto label with the qemu_chr_fe_wait_connected,
> the vhost_user_cleanup will set user->chr be NULL,but the fe handler
> vhost_user_blk_event is still work on the env.
>
> If the vhost slave(eg:spdk) has not been done,we will see the qemu-kvm
> crash after reopen the vhost-user-blk dev:
The English up to here is a little awkward. Maybe rather:
When a vhost-user-blk backend, such as SPDK restarts, all of the
backend's vhost devs will be reconnected. If
vhost_user_blk_device_realize() fails at qemu_chr_fe_wait_connected(),
goto virtio_err will be executed. This in turn calls
vhost_user_cleanup which sets user->chr to NULL. This is problematic
because the qemu_chr_fe_handler will still be active and will crash if
the backend comes back up and reopens the chardev.
> gdb debug info from qemu-kvm-2.10:
> [Thread debugging using libthread_db enabled]
> Using host libthread_db library "/lib64/libthread_db.so.1".
> Core was generated by `/usr/libexec/qemu-kvm -name guest=db1ae942ac9c5486bf93c7baac5fcce6,debug-thread'.
I don't think you need these three lines:
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Core was generated by `/usr/libexec/qemu-kvm -name
guest=db1ae942ac9c5486bf93c7baac5fcce6,debug-thread'.
> Program terminated with signal 11, Segmentation fault.
> #0 qemu_chr_fe_set_msgfds (be=0x0, fds=0x0, num=0) at chardev/char-fe.c:144
> 144 Chardev *s = be->chr;
>
> So,we must reset the fe handler after the goto label virtio_err.
>
> Signed-off-by: Bobo Du <dubo163@126.com>
Reviewed-by: Raphael Norwitz <raphael.norwitz@nutanix.com>
> ---
> hw/block/vhost-user-blk.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/hw/block/vhost-user-blk.c b/hw/block/vhost-user-blk.c
> index da4fbf9084..c90687ab82 100644
> --- a/hw/block/vhost-user-blk.c
> +++ b/hw/block/vhost-user-blk.c
> @@ -507,6 +507,8 @@ virtio_err:
> }
> g_free(s->virtqs);
> virtio_cleanup(vdev);
> + qemu_chr_fe_set_handlers(&s->chardev, NULL, NULL, NULL,
> + NULL, NULL, NULL, false);
> vhost_user_cleanup(&s->vhost_user);
> }
>
> --
> 2.17.0
>
>
next prev parent reply other threads:[~2021-01-20 18:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-20 3:50 [PATCH] vhost-user-blk.c:fix the qemu-kvm crash in the vhost-user-blk env Bobo Du
2021-01-20 18:50 ` Raphael Norwitz [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-01-20 3:44 Bobo Du
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=CAFubqFtX-vWJ8ajnxVeh9r677Pr1mxvRayj7aOfCAeduWTf-hA@mail.gmail.com \
--to=raphael.s.norwitz@gmail.com \
--cc=dubo163@126.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).