From: Stefan Hajnoczi <stefanha@redhat.com>
To: Fam Zheng <famz@redhat.com>
Cc: Stefan Hajnoczi <stefanha@gmail.com>,
Kevin Wolf <kwolf@redhat.com>,
pbonzini@redhat.com, qemu-devel@nongnu.org,
qemu-block@nongnu.org
Subject: Re: [Qemu-devel] [Qemu-block] [PATCH] vl: introduce vm_shutdown()
Date: Wed, 28 Feb 2018 09:40:37 +0000 [thread overview]
Message-ID: <20180228094037.GA13990@stefanha-x1.localdomain> (raw)
In-Reply-To: <20180228015813.GC21336@lemon.usersys.redhat.com>
[-- Attachment #1: Type: text/plain, Size: 2839 bytes --]
On Wed, Feb 28, 2018 at 09:58:13AM +0800, Fam Zheng wrote:
> On Tue, 02/27 15:30, Stefan Hajnoczi wrote:
> > On Fri, Feb 23, 2018 at 04:20:44PM +0800, Fam Zheng wrote:
> > > On Tue, 02/20 13:10, Stefan Hajnoczi wrote:
> > > > 1. virtio_scsi_handle_cmd_vq() racing with iothread_stop_all() hits the
> > > > virtio_scsi_ctx_check() assertion failure because the BDS AioContext
> > > > has been modified by iothread_stop_all().
> > >
> > > Does this patch fix the issue completely? IIUC virtio_scsi_handle_cmd can
> > > already be entered at the time of main thread calling virtio_scsi_clear_aio(),
> > > so this race condition still exists:
> > >
> > > main thread iothread
> > > -----------------------------------------------------------------------------
> > > vm_shutdown
> > > ...
> > > virtio_bus_stop_ioeventfd
> > > virtio_scsi_dataplane_stop
> > > aio_poll()
> > > ...
> > > virtio_scsi_data_plane_handle_cmd()
> > > aio_context_acquire(s->ctx)
> > > virtio_scsi_acquire(s).enter
> > > virtio_scsi_clear_aio()
> > > aio_context_release(s->ctx)
> > > virtio_scsi_acquire(s).return
> > > virtio_scsi_handle_cmd_vq()
> > > ...
> > > virtqueue_pop()
> > >
> > > Is it possible that the above virtqueue_pop() still returns one element that was
> > > queued before vm_shutdown() was called?
> >
> > No, it can't because virtio_scsi_clear_aio() invokes
> > virtio_queue_host_notifier_aio_read(&vq->host_notifier) to process the
> > virtqueue. By the time we get back to iothread's
> > virtio_scsi_data_plane_handle_cmd() the virtqueue is already empty.
> >
> > Vcpus have been paused so no additional elements can slip into the
> > virtqueue.
>
> So there is:
>
> static void virtio_queue_host_notifier_aio_read(EventNotifier *n)
> {
> VirtQueue *vq = container_of(n, VirtQueue, host_notifier);
> if (event_notifier_test_and_clear(n)) {
> virtio_queue_notify_aio_vq(vq);
> }
> }
>
> Guest kicks after adding an element to VQ, but we check ioeventfd before trying
> virtqueue_pop(). Is that a problem? If VCPUs are paused after enqueuing but
> before kicking VQ, the ioeventfd is not set, the virtqueue is not processed
> here.
You are right.
This race condition also affects the existing 'stop' command, where
ioeventfd is disabled in the same way. I'll send a v2 with a patch to
fix this.
Stefan
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 455 bytes --]
prev parent reply other threads:[~2018-02-28 9:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-20 13:10 [Qemu-devel] [PATCH] vl: introduce vm_shutdown() Stefan Hajnoczi
2018-02-23 8:20 ` Fam Zheng
2018-02-27 15:30 ` [Qemu-devel] [Qemu-block] " Stefan Hajnoczi
2018-02-28 1:58 ` Fam Zheng
2018-02-28 9:40 ` Stefan Hajnoczi [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=20180228094037.GA13990@stefanha-x1.localdomain \
--to=stefanha@redhat.com \
--cc=famz@redhat.com \
--cc=kwolf@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.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).