From: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
To: qemu-block@nongnu.org, qemu-devel@nongnu.org
Cc: mreitz@redhat.com, kwolf@redhat.com, jcody@redhat.com,
pbonzini@redhat.com, dplotnikov@virtuozzo.com, den@openvz.org,
vsementsov@virtuozzo.com, qemu-stable@nongnu.org
Subject: [Qemu-devel] [PATCH v2 0/2] mirror dead-lock
Date: Thu, 29 Nov 2018 13:17:59 +0300 [thread overview]
Message-ID: <20181129101801.6421-1-vsementsov@virtuozzo.com> (raw)
Hi all!
v2: add fix:)
We've faced the following mirror bug:
Just run mirror on qcow2 image more than 1G, and qemu is in dead lock.
Dead lock described in 01, in short, we have extra aio_context_acquire
and aio_context_release around blk_aio_pwritev in mirror_read_complete.
So, write may yield to the main loop, and aio context is acquired. Main
loop than hangs on trying to lock BQL, which is locked by cpu thread,
and the cpu thread hangs on trying to acquire aio context.
Hm, now the thing looks fixed, by I still have a questions:
Is it a common thing, that we can't yield inside
aio_context_acquire/release ?
Was commit b9e413dd3756
"block: explicitly acquire aiocontext in aio callbacks that need it"
wrong? Why it added these acquire/release, when it is written in
multiple-iothreads.txt, that "Side note: the best way to schedule a function
call across threads is to call aio_bh_schedule_oneshot(). No acquire/release
or locking is needed."
Can someone in short describe, what BQL and aio context lock means, what they
protect, and haw they should cooperate?
Vladimir Sementsov-Ogievskiy (2):
mirror: fix dead-lock
iotests: simple mirror test with kvm on 1G image
block/mirror.c | 13 ++++-----
tests/qemu-iotests/235 | 59 ++++++++++++++++++++++++++++++++++++++
tests/qemu-iotests/235.out | 1 +
tests/qemu-iotests/group | 1 +
4 files changed, 66 insertions(+), 8 deletions(-)
create mode 100755 tests/qemu-iotests/235
create mode 100644 tests/qemu-iotests/235.out
--
2.18.0
next reply other threads:[~2018-11-29 10:18 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-29 10:17 Vladimir Sementsov-Ogievskiy [this message]
2018-11-29 10:18 ` [Qemu-devel] [PATCH v2 1/2] mirror: fix dead-lock Vladimir Sementsov-Ogievskiy
2018-11-30 12:36 ` Max Reitz
2018-11-29 10:18 ` [Qemu-devel] [PATCH v2 2/2] iotests: simple mirror test with kvm on 1G image Vladimir Sementsov-Ogievskiy
2018-11-30 12:19 ` Kevin Wolf
2018-11-30 12:30 ` Max Reitz
2018-11-30 13:06 ` Vladimir Sementsov-Ogievskiy
2018-11-30 13:13 ` Max Reitz
2018-11-30 13:48 ` Vladimir Sementsov-Ogievskiy
2018-11-30 14:10 ` Kevin Wolf
2018-11-30 14:51 ` Vladimir Sementsov-Ogievskiy
2018-11-30 14:59 ` Max Reitz
2018-11-30 15:24 ` Vladimir Sementsov-Ogievskiy
2018-11-30 15:33 ` Max Reitz
2018-11-30 16:14 ` Vladimir Sementsov-Ogievskiy
2018-11-30 12:33 ` Max Reitz
2018-11-29 14:14 ` [Qemu-devel] [Qemu-devel for-3.1?] [PATCH v2 0/2] mirror dead-lock Eric Blake
2018-11-30 12:52 ` Max Reitz
2018-12-03 13:59 ` [Qemu-devel] " Max Reitz
2018-12-03 14:13 ` Vladimir Sementsov-Ogievskiy
2018-12-03 14:26 ` Max Reitz
2018-12-03 17:06 ` Eric Blake
2018-12-03 15:07 ` Peter Maydell
2018-12-03 16:06 ` 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=20181129101801.6421-1-vsementsov@virtuozzo.com \
--to=vsementsov@virtuozzo.com \
--cc=den@openvz.org \
--cc=dplotnikov@virtuozzo.com \
--cc=jcody@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@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).