From: "Michael S. Tsirkin" <mst@redhat.com>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: "peter.maydell@linaro.org" <peter.maydell@linaro.org>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Raphael Norwitz <raphael.norwitz@nutanix.com>,
"pbonzini@redhat.com" <pbonzini@redhat.com>,
"eblake@redhat.com" <eblake@redhat.com>,
"sgarzare@redhat.com" <sgarzare@redhat.com>
Subject: Re: [PATCH v6] Work around vhost-user-blk-test hang
Date: Tue, 19 Oct 2021 10:39:17 -0400 [thread overview]
Message-ID: <20211019103834-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <YW7O2q/UaKl3Ao09@stefanha-x1.localdomain>
On Tue, Oct 19, 2021 at 02:57:46PM +0100, Stefan Hajnoczi wrote:
> On Thu, Oct 14, 2021 at 04:32:23AM +0000, Raphael Norwitz wrote:
> > The vhost-user-blk-test qtest has been hanging intermittently for a
> > while. The root cause is not yet fully understood, but the hang is
> > impacting enough users that it is important to merge a workaround for
> > it.
> >
> > The race which causes the hang occurs early on in vhost-user setup,
> > where a vhost-user message is never received by the backend. Forcing
> > QEMU to wait until the storage-daemon has had some time to initialize
> > prevents the hang. Thus the existing storage-daemon pidfile option can
> > be used to implement a workaround cleanly and effectively, since it
> > creates a file only once the storage-daemon initialization is complete.
> >
> > This change implements a workaround for the vhost-user-blk-test hang by
> > making QEMU wait until the storage-daemon has written out a pidfile
> > before attempting to connect and send messages over the vhost-user
> > socket.
> >
> > Some relevent mailing list discussions:
> >
> > [1] https://lore.kernel.org/qemu-devel/CAFEAcA8kYpz9LiPNxnWJAPSjc=nv532bEdyfynaBeMeohqBp3A@mail.gmail.com/
> > [2] https://lore.kernel.org/qemu-devel/YWaky%2FKVbS%2FKZjlV@stefanha-x1.localdomain/
>
> I sent a fix for the hang so the workaround is no longer needed:
> "[PATCH] vhost-user-blk-test: pass vhost-user socket fds to QSD"
>
> Stefan
Woot! Thanks a bunch Stefan! Great job debugging this!
--
MST
prev parent reply other threads:[~2021-10-19 15:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-14 4:32 [PATCH v6] Work around vhost-user-blk-test hang Raphael Norwitz
2021-10-18 21:50 ` Michael S. Tsirkin
2021-10-18 22:33 ` Raphael Norwitz
2021-10-19 6:20 ` Michael S. Tsirkin
2021-10-19 13:57 ` Stefan Hajnoczi
2021-10-19 14:39 ` Michael S. Tsirkin [this message]
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=20211019103834-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=eblake@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=raphael.norwitz@nutanix.com \
--cc=sgarzare@redhat.com \
--cc=stefanha@redhat.com \
/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).