From: Thomas Huth <thuth@redhat.com>
To: Milan Zamazal <mzamazal@redhat.com>, qemu-devel@nongnu.org
Cc: "Fabiano Rosas" <farosas@suse.de>,
"Michael S. Tsirkin" <mst@redhat.com>,
"Peter Maydell" <peter.maydell@linaro.org>,
"Laurent Vivier" <lvivier@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Richard Henderson" <richard.henderson@linaro.org>,
"Alex Bennée" <alex.bennee@linaro.org>
Subject: Re: [PATCH] hw/virtio: Add a protection against duplicate vu_scmi_stop calls
Date: Thu, 20 Jul 2023 12:55:31 +0200 [thread overview]
Message-ID: <655d66c7-9f42-0610-d1f8-224687e29761@redhat.com> (raw)
In-Reply-To: <20230720101037.2161450-1-mzamazal@redhat.com>
On 20/07/2023 12.10, Milan Zamazal wrote:
> The QEMU CI fails in virtio-scmi test occasionally. As reported by
> Thomas Huth, this happens most likely when the system is loaded and it
> fails with the following error:
>
> qemu-system-aarch64: ../../devel/qemu/hw/pci/msix.c:659:
> msix_unset_vector_notifiers: Assertion `dev->msix_vector_use_notifier && dev->msix_vector_release_notifier' failed.
> ../../devel/qemu/tests/qtest/libqtest.c:200: kill_qemu() detected QEMU death from signal 6 (Aborted) (core dumped)
>
> As discovered by Fabiano Rosas, the cause is a duplicate invocation of
> msix_unset_vector_notifiers via duplicate vu_scmi_stop calls:
>
> msix_unset_vector_notifiers
> virtio_pci_set_guest_notifiers
> vu_scmi_stop
> vu_scmi_disconnect
> ...
> qemu_chr_write_buffer
>
> msix_unset_vector_notifiers
> virtio_pci_set_guest_notifiers
> vu_scmi_stop
> vu_scmi_set_status
> ...
> qemu_cleanup
>
> While vu_scmi_stop calls are protected by vhost_dev_is_started()
> check, it's apparently not enough. vhost-user-blk and vhost-user-gpio
> use an extra protection, see f5b22d06fb (vhost: recheck dev state in
> the vhost_migration_log routine) for the motivation. Let's use the
> same in vhost-user-scmi, which fixes the failure above.
>
> Fixes: a5dab090e142 ("hw/virtio: Add boilerplate for vhost-user-scmi device")
> Signed-off-by: Milan Zamazal <mzamazal@redhat.com>
> ---
> hw/virtio/vhost-user-scmi.c | 7 +++++++
> include/hw/virtio/vhost-user-scmi.h | 1 +
> 2 files changed, 8 insertions(+)
Thanks, that fixes the problem for me!
Tested-by: Thomas Huth <thuth@redhat.com>
next prev parent reply other threads:[~2023-07-20 10:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-20 10:10 [PATCH] hw/virtio: Add a protection against duplicate vu_scmi_stop calls Milan Zamazal
2023-07-20 10:55 ` Thomas Huth [this message]
2023-07-20 12:30 ` Fabiano Rosas
2023-08-03 7:10 ` Milan Zamazal
2023-08-03 7:38 ` Thomas Huth
2023-08-03 9:50 ` Michael S. Tsirkin
2023-08-03 10:46 ` Thomas Huth
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=655d66c7-9f42-0610-d1f8-224687e29761@redhat.com \
--to=thuth@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=farosas@suse.de \
--cc=lvivier@redhat.com \
--cc=mst@redhat.com \
--cc=mzamazal@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.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).