From: Kevin Wolf <kwolf@redhat.com>
To: qemu-block@nongnu.org
Cc: kwolf@redhat.com, vsementsov@virtuozzo.com, s.reiter@proxmox.com,
qemu-devel@nongnu.org, dietmar@proxmox.com, stefanha@redhat.com,
mreitz@redhat.com, t.lamprecht@proxmox.com
Subject: [PATCH for-5.0 v3 0/3] block: Fix blk->in_flight during blk_wait_while_drained()
Date: Tue, 7 Apr 2020 14:12:56 +0200 [thread overview]
Message-ID: <20200407121259.21350-1-kwolf@redhat.com> (raw)
This fixes deadlocks when draining a BlockBackend in an iothread that
receives new requests at the same time.
v3:
- Call blk_inc/dec_in_flight() in blk_prw() rather than inside the
coroutines [Max]
v2:
- Rework the whole thing so that direct callers of blk_co_*() aren't
broken after the series [Max]
Kevin Wolf (3):
block-backend: Reorder flush/pdiscard function definitions
block: Increase BB.in_flight for coroutine and sync interfaces
block: Fix blk->in_flight during blk_wait_while_drained()
include/sysemu/block-backend.h | 1 -
block/block-backend.c | 206 ++++++++++++++++++++-------------
2 files changed, 128 insertions(+), 79 deletions(-)
--
2.20.1
next reply other threads:[~2020-04-07 12:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-07 12:12 Kevin Wolf [this message]
2020-04-07 12:12 ` [PATCH for-5.0 v3 1/3] block-backend: Reorder flush/pdiscard function definitions Kevin Wolf
2020-04-07 12:12 ` [PATCH for-5.0 v3 2/3] block: Increase BB.in_flight for coroutine and sync interfaces Kevin Wolf
2020-04-07 12:54 ` Max Reitz
2020-04-07 14:22 ` Vladimir Sementsov-Ogievskiy
2020-04-07 14:42 ` Kevin Wolf
2020-04-07 14:56 ` Vladimir Sementsov-Ogievskiy
2020-04-07 16:27 ` Kevin Wolf
2020-04-07 17:36 ` Vladimir Sementsov-Ogievskiy
2020-04-07 12:12 ` [PATCH for-5.0 v3 3/3] block: Fix blk->in_flight during blk_wait_while_drained() 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=20200407121259.21350-1-kwolf@redhat.com \
--to=kwolf@redhat.com \
--cc=dietmar@proxmox.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=s.reiter@proxmox.com \
--cc=stefanha@redhat.com \
--cc=t.lamprecht@proxmox.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).