qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>
To: qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>,
	Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>
Subject: [Qemu-devel] [PATCH 0/3] block: fix and detect qemu_aio_wait() issues
Date: Wed, 30 Nov 2011 12:23:40 +0000	[thread overview]
Message-ID: <1322655824-31778-1-git-send-email-stefanha@linux.vnet.ibm.com> (raw)

This series fixes an issue where qemu_aio_flush() would return to IDE hardware
emulation with requests still pending.  Kevin Wolf <kwolf@redhat.com> found it
in the block tree before qemu.git/master merge, so qemu.git/master is not
affected and these patches are against his tree.

A recent interaction between copy-on-read and "qcow2: Unlock during COW"
emphasized the need for strong assertion checking.  Patch 1 fixes an assertion
failure with qcow2 images in hw/ide/pci.c:bmdma_cmd_writeb().

Patches 2 and 3 then introduce assertions that detect
wait_for_overlapping_requests() deadlock and broken qemu_aio_wait().  In the
future we will have better information if issues related to qemu_aio_wait()
come up.

I have run qemu-iotests for qcow2 and qed.  I have also performed a RHEL6 guest
install to qed and tested booting the guest with IDE and qcow2.

Stefan Hajnoczi (3):
  qcow2: avoid reentrant bdrv_read() in copy_sectors()
  block: wait_for_overlapping_requests() deadlock detection
  block: convert qemu_aio_flush() calls to bdrv_drain_all()

 block-migration.c     |    2 +-
 block.c               |   27 +++++++++++++++++++++++++++
 block.h               |    1 +
 block/qcow2-cluster.c |   27 +++++++++++++++++++--------
 blockdev.c            |    4 ++--
 cpus.c                |    2 +-
 hw/ide/macio.c        |    5 +++--
 hw/ide/pci.c          |    2 +-
 hw/virtio-blk.c       |    2 +-
 hw/xen_platform.c     |    2 +-
 qemu-io.c             |    4 ++--
 savevm.c              |    2 +-
 xen-mapcache.c        |    2 +-
 13 files changed, 61 insertions(+), 21 deletions(-)

-- 
1.7.7.3

             reply	other threads:[~2011-11-30 12:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-30 12:23 Stefan Hajnoczi [this message]
2011-11-30 12:23 ` [Qemu-devel] [PATCH 1/3] qcow2: avoid reentrant bdrv_read() in copy_sectors() Stefan Hajnoczi
2011-11-30 12:23 ` [Qemu-devel] [PATCH 2/3] block: wait_for_overlapping_requests() deadlock detection Stefan Hajnoczi
2011-11-30 12:23 ` [Qemu-devel] [PATCH 3/3] block: convert qemu_aio_flush() calls to bdrv_drain_all() Stefan Hajnoczi
2011-11-30 12:28   ` Christoph Hellwig
2011-11-30 12:54     ` Stefan Hajnoczi
2011-12-05 13:57 ` [Qemu-devel] [PATCH 0/3] block: fix and detect qemu_aio_wait() issues Kevin Wolf

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=1322655824-31778-1-git-send-email-stefanha@linux.vnet.ibm.com \
    --to=stefanha@linux.vnet.ibm.com \
    --cc=kwolf@redhat.com \
    --cc=qemu-devel@nongnu.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).