qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@gmail.com>
To: Fam Zheng <famz@redhat.com>
Cc: Stefan Hajnoczi <stefanha@redhat.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: Tue, 27 Feb 2018 15:30:25 +0000	[thread overview]
Message-ID: <20180227153025.GA32480@stefanha-x1.localdomain> (raw)
In-Reply-To: <20180223082044.GB31530@lemon.usersys.redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1876 bytes --]

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.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 455 bytes --]

  reply	other threads:[~2018-02-27 15:30 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   ` Stefan Hajnoczi [this message]
2018-02-28  1:58     ` [Qemu-devel] [Qemu-block] " Fam Zheng
2018-02-28  9:40       ` Stefan Hajnoczi

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=20180227153025.GA32480@stefanha-x1.localdomain \
    --to=stefanha@gmail.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@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).