From: Eric Blake <eblake@redhat.com>
To: Hanna Reitz <hreitz@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
Emanuele Giuseppe Esposito <eesposit@redhat.com>,
qemu-devel@nongnu.org, qemu-block@nongnu.org,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [PATCH 1/4] block: Classify bdrv_get_flags() as I/O function
Date: Wed, 27 Apr 2022 08:14:59 -0500 [thread overview]
Message-ID: <20220427131459.ncb73rqtp47xluxx@redhat.com> (raw)
In-Reply-To: <20220427114057.36651-2-hreitz@redhat.com>
On Wed, Apr 27, 2022 at 01:40:54PM +0200, Hanna Reitz wrote:
> This function is safe to call in an I/O context, and qcow2_do_open()
> does so (invoked in an I/O context by qcow2_co_invalidate_cache()).
>
> Signed-off-by: Hanna Reitz <hreitz@redhat.com>
> ---
> include/block/block-global-state.h | 1 -
> include/block/block-io.h | 1 +
> block.c | 2 +-
> 3 files changed, 2 insertions(+), 2 deletions(-)
Reviewed-by: Eric Blake <eblake@redhat.com>
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
next prev parent reply other threads:[~2022-04-27 13:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-27 11:40 [PATCH 0/4] Revert "main-loop: Disable GLOBAL_STATE_CODE() assertions" Hanna Reitz
2022-04-27 11:40 ` [PATCH 1/4] block: Classify bdrv_get_flags() as I/O function Hanna Reitz
2022-04-27 13:14 ` Eric Blake [this message]
2022-04-27 11:40 ` [PATCH 2/4] qcow2: Do not reopen data_file in invalidate_cache Hanna Reitz
2022-04-27 13:20 ` Eric Blake
2022-04-27 16:05 ` Kevin Wolf
2022-04-27 11:40 ` [PATCH 3/4] Revert "main-loop: Disable GLOBAL_STATE_CODE() assertions" Hanna Reitz
2022-04-27 13:22 ` Eric Blake
2022-04-27 11:40 ` [PATCH 4/4] iotests: Add regression test for issue 945 Hanna Reitz
2022-04-27 13:52 ` Eric Blake
2022-04-27 16:13 ` [PATCH 0/4] Revert "main-loop: Disable GLOBAL_STATE_CODE() assertions" 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=20220427131459.ncb73rqtp47xluxx@redhat.com \
--to=eblake@redhat.com \
--cc=eesposit@redhat.com \
--cc=hreitz@redhat.com \
--cc=kwolf@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-block@nongnu.org \
--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).