From: Stefan Hajnoczi <stefanha@redhat.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: Fam Zheng <famz@redhat.com>,
qemu-block@nongnu.org, armbru@redhat.com, qemu-devel@nongnu.org,
mreitz@redhat.com, pbonzini@redhat.com
Subject: Re: [Qemu-devel] [Qemu-block] [RFC PATCH 0/7] Fix transactional snapshot with virtio-blk dataplane
Date: Fri, 8 May 2015 09:46:37 +0100 [thread overview]
Message-ID: <20150508084637.GB11717@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <20150507134343.GM13985@stefanha-thinkpad.redhat.com>
[-- Attachment #1: Type: text/plain, Size: 2899 bytes --]
On Thu, May 07, 2015 at 02:43:43PM +0100, Stefan Hajnoczi wrote:
> On Wed, May 06, 2015 at 07:23:32PM +0800, Fam Zheng wrote:
> > Reported by Paolo.
> >
> > Unlike the iohandler in main loop, iothreads currently process the event
> > notifier used as virtio-blk ioeventfd in all nested aio_poll. This is dangerous
> > without proper protection, because guest requests could sneak to block layer
> > where they mustn't.
> >
> > For example, a QMP transaction may involve multiple bdrv_drain_all() in
> > handling the list of AioContext it works on. If an aio_poll in one of the
> > bdrv_drain_all() happens to process a guest VQ kick by dispatching the
> > ioeventfd event, a new guest write is then submitted, and voila, the
> > transaction semantics is violated.
> >
> > This series avoids this problem by disabling virtio-blk handlers during
> > bdrv_drain_all() and transactions.
> >
> > Notes:
> >
> > If the general approach is right, other transaction types could get the
> > blockers similarly, in next revision. And some related bdrv_drain_all() could
> > also be changed to bdrv_drain().
> >
> > virtio-scsi-dataplane will be a bit more complicated, but still doable. It
> > would probably need one more interface abstraction between scsi-disk, scsi-bus
> > and virtio-scsi.
> >
> > Although other devices don't have a pause/resume callback yet, the
> > blk_check_request, which returns -EBUSY if "device io" op blocker is set, could
> > hopefully cover most cases already.
> >
> > Timers and block jobs also generate IO, but it should be fine as long as they
> > don't change guest visible data, which is true AFAICT.
> >
> >
> > Fam Zheng (7):
> > block: Add op blocker type "device IO"
> > block: Block "device IO" during bdrv_drain and bdrv_drain_all
> > block: Add op blocker notifier list
> > block-backend: Add blk_op_blocker_add_notifier
> > virtio-blk: Move complete_request to 'ops' structure
> > virtio-blk: Don't handle output when there is "device IO" op blocker
> > blockdev: Add "device IO" op blocker during snapshot transaction
> >
> > block.c | 20 ++++++++++++
> > block/block-backend.c | 10 ++++++
> > block/io.c | 12 +++++++
> > blockdev.c | 7 +++++
> > hw/block/dataplane/virtio-blk.c | 36 ++++++++++++++++++---
> > hw/block/virtio-blk.c | 69 +++++++++++++++++++++++++++++++++++++++--
> > include/block/block.h | 9 ++++++
> > include/block/block_int.h | 3 ++
> > include/hw/virtio/virtio-blk.h | 17 ++++++++--
> > include/sysemu/block-backend.h | 2 ++
> > 10 files changed, 174 insertions(+), 11 deletions(-)
>
> Please also add a listener to nbd.c so NBD exports cannot submit I/O
> during bdrv_drain_all().
qmp_transaction probably also needs this.
Stefan
[-- Attachment #2: Type: application/pgp-signature, Size: 473 bytes --]
prev parent reply other threads:[~2015-05-08 8:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-06 11:23 [Qemu-devel] [RFC PATCH 0/7] Fix transactional snapshot with virtio-blk dataplane Fam Zheng
2015-05-06 11:23 ` [Qemu-devel] [RFC PATCH 1/7] block: Add op blocker type "device IO" Fam Zheng
2015-05-06 11:23 ` [Qemu-devel] [RFC PATCH 2/7] block: Block "device IO" during bdrv_drain and bdrv_drain_all Fam Zheng
2015-05-06 11:23 ` [Qemu-devel] [RFC PATCH 3/7] block: Add op blocker notifier list Fam Zheng
2015-05-06 14:22 ` Paolo Bonzini
2015-05-06 15:03 ` Fam Zheng
2015-05-06 11:23 ` [Qemu-devel] [RFC PATCH 4/7] block-backend: Add blk_op_blocker_add_notifier Fam Zheng
2015-05-06 11:23 ` [Qemu-devel] [RFC PATCH 5/7] virtio-blk: Move complete_request to 'ops' structure Fam Zheng
2015-05-06 11:23 ` [Qemu-devel] [RFC PATCH 6/7] virtio-blk: Don't handle output when there is "device IO" op blocker Fam Zheng
2015-05-06 12:07 ` Paolo Bonzini
2015-05-06 12:20 ` Fam Zheng
2015-05-06 14:18 ` Paolo Bonzini
2015-05-06 11:23 ` [Qemu-devel] [RFC PATCH 7/7] blockdev: Add "device IO" op blocker during snapshot transaction Fam Zheng
2015-05-07 13:43 ` [Qemu-devel] [Qemu-block] [RFC PATCH 0/7] Fix transactional snapshot with virtio-blk dataplane Stefan Hajnoczi
2015-05-08 8:46 ` 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=20150508084637.GB11717@stefanha-thinkpad.redhat.com \
--to=stefanha@redhat.com \
--cc=armbru@redhat.com \
--cc=famz@redhat.com \
--cc=mreitz@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).