From: Kevin Wolf <kwolf@redhat.com>
To: qemu-block@nongnu.org
Cc: kwolf@redhat.com, hreitz@redhat.com, vsementsov@virtuozzo.com,
qinwang@redhat.com, qemu-devel@nongnu.org
Subject: [PATCH 0/2] block: Fix crash in blockdev-reopen with iothreads
Date: Thu, 3 Feb 2022 15:05:32 +0100 [thread overview]
Message-ID: <20220203140534.36522-1-kwolf@redhat.com> (raw)
Kevin Wolf (2):
block: Lock AioContext for drain_end in blockdev-reopen
iotests: Test blockdev-reopen with iothreads and throttling
blockdev.c | 11 ++++++++++-
tests/qemu-iotests/245 | 36 +++++++++++++++++++++++++++++++++---
tests/qemu-iotests/245.out | 4 ++--
3 files changed, 45 insertions(+), 6 deletions(-)
--
2.31.1
next reply other threads:[~2022-02-03 14:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-03 14:05 Kevin Wolf [this message]
2022-02-03 14:05 ` [PATCH 1/2] block: Lock AioContext for drain_end in blockdev-reopen Kevin Wolf
2022-02-03 16:37 ` Hanna Reitz
2022-02-03 14:05 ` [PATCH 2/2] iotests: Test blockdev-reopen with iothreads and throttling Kevin Wolf
2022-02-03 16:45 ` Hanna Reitz
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=20220203140534.36522-1-kwolf@redhat.com \
--to=kwolf@redhat.com \
--cc=hreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=qinwang@redhat.com \
--cc=vsementsov@virtuozzo.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).