From: Paolo Bonzini <pbonzini@redhat.com>
To: Eric Blake <eblake@redhat.com>
Cc: qemu-devel@nongnu.org, Alberto Campinho Faria <afaria@redhat.com>
Subject: Re: [PATCH v2 07/26] block: add missing coroutine_fn annotations
Date: Sat, 14 May 2022 11:54:07 +0200 [thread overview]
Message-ID: <ab3b2d59-109c-43d4-f97b-1c8ee1ee1f2c@redhat.com> (raw)
In-Reply-To: <20220513212613.laydrlckh63wett4@redhat.com>
On 5/13/22 23:26, Eric Blake wrote:
>> +int coroutine_fn blk_pwrite_zeroes(BlockBackend *blk, int64_t offset,
>> + int64_t bytes, BdrvRequestFlags flags)
> Tracking down all callers of blk_pwrite_zeroes is not as trivial as in
> the previous patches. But the very first one I checked:
> block.c: create_file_fallback_zero_first_sector()
>
> is neither marked coroutine_fn, nor does it have the "if
> (qemu_in_coroutine())" guard.
That one in particular _should_ be coroutine_fn;
bdrv_co_create_opts_simple is the only caller. This is probably a
limitation of the thread-safety annotations that I used to generate this
patchset: the compiler does limited inter-procedural analysis which for
us means missing some potential coroutine_fn additions.
But I agree that blk_pwrite_zeros shouldn't be a coroutine_fn, because
of fuse_fallocate and block_load. Alberto, this function is another
candidate for adding a blk_co_pwrite_zeros + a matching
generated_co_wrapper.
Paolo
> And block.c is not touched in this
> patch series, per the diffstat in 0/26. Am I missing something?
next prev parent reply other threads:[~2022-05-14 9:56 UTC|newest]
Thread overview: 66+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-09 10:29 [PATCH v2 00/26] block: fix coroutine_fn annotations Paolo Bonzini
2022-05-09 10:29 ` [PATCH v2 01/26] block: remove incorrect " Paolo Bonzini
2022-05-10 15:03 ` Eric Blake
2022-07-04 12:54 ` Alberto Faria
2022-05-09 10:29 ` [PATCH v2 02/26] qcow2: " Paolo Bonzini
2022-05-10 15:04 ` Eric Blake
2022-07-04 12:56 ` Alberto Faria
2022-05-09 10:29 ` [PATCH v2 03/26] nbd: " Paolo Bonzini
2022-05-10 15:05 ` Eric Blake
2022-07-04 12:56 ` Alberto Faria
2022-05-09 10:29 ` [PATCH v2 04/26] coroutine: " Paolo Bonzini
2022-05-10 15:12 ` Eric Blake
2022-07-04 12:57 ` Alberto Faria
2022-05-09 10:29 ` [PATCH v2 05/26] blkdebug: add missing " Paolo Bonzini
2022-05-10 15:30 ` Eric Blake
2022-05-09 10:29 ` [PATCH v2 06/26] blkverify: " Paolo Bonzini
2022-05-10 15:59 ` Eric Blake
2022-07-04 12:57 ` Alberto Faria
2022-05-09 10:30 ` [PATCH v2 07/26] block: " Paolo Bonzini
2022-05-13 21:26 ` Eric Blake
2022-05-14 9:54 ` Paolo Bonzini [this message]
2022-05-16 18:49 ` Alberto Faria
2022-05-17 9:51 ` Paolo Bonzini
2022-05-09 10:30 ` [PATCH v2 08/26] file-posix: " Paolo Bonzini
2022-05-13 21:52 ` Eric Blake
2022-07-04 12:57 ` Alberto Faria
2022-05-09 10:30 ` [PATCH v2 09/26] iscsi: " Paolo Bonzini
2022-05-18 14:44 ` Eric Blake
2022-07-04 12:58 ` Alberto Faria
2022-05-09 10:30 ` [PATCH v2 10/26] nbd: " Paolo Bonzini
2022-05-18 14:50 ` Eric Blake
2022-07-04 12:58 ` Alberto Faria
2022-05-09 10:30 ` [PATCH v2 11/26] nfs: " Paolo Bonzini
2022-07-04 12:59 ` Alberto Faria
2022-05-09 10:30 ` [PATCH v2 12/26] nvme: " Paolo Bonzini
2022-07-04 12:59 ` Alberto Faria
2022-05-09 10:30 ` [PATCH v2 13/26] parallels: " Paolo Bonzini
2022-07-04 12:59 ` Alberto Faria
2022-05-09 10:30 ` [PATCH v2 14/26] qcow2: " Paolo Bonzini
2022-07-04 12:59 ` Alberto Faria
2022-05-09 10:30 ` [PATCH v2 15/26] copy-before-write: " Paolo Bonzini
2022-07-04 12:59 ` Alberto Faria
2022-05-09 10:30 ` [PATCH v2 16/26] curl: " Paolo Bonzini
2022-07-04 13:00 ` Alberto Faria
2022-05-09 10:30 ` [PATCH v2 17/26] qed: " Paolo Bonzini
2022-07-04 13:01 ` Alberto Faria
2022-05-09 10:30 ` [PATCH v2 18/26] quorum: " Paolo Bonzini
2022-07-04 13:01 ` Alberto Faria
2022-05-09 10:30 ` [PATCH v2 19/26] throttle: " Paolo Bonzini
2022-07-04 13:02 ` Alberto Faria
2022-05-09 10:30 ` [PATCH v2 20/26] vmdk: " Paolo Bonzini
2022-07-04 13:02 ` Alberto Faria
2022-05-09 10:30 ` [PATCH v2 21/26] job: " Paolo Bonzini
2022-07-04 13:02 ` Alberto Faria
2022-05-09 10:30 ` [PATCH v2 22/26] coroutine-lock: " Paolo Bonzini
2022-07-04 13:03 ` Alberto Faria
2022-05-09 10:30 ` [PATCH v2 23/26] raw-format: " Paolo Bonzini
2022-07-04 13:03 ` Alberto Faria
2022-05-09 10:30 ` [PATCH v2 24/26] 9p: " Paolo Bonzini
2022-07-04 13:03 ` Alberto Faria
2022-05-09 10:30 ` [PATCH v2 25/26] migration: " Paolo Bonzini
2022-07-04 13:03 ` Alberto Faria
2022-05-09 10:30 ` [PATCH v2 26/26] test-coroutine: " Paolo Bonzini
2022-07-04 13:03 ` Alberto Faria
2022-05-09 11:53 ` [PATCH v2 00/26] block: fix " Daniel P. Berrangé
2022-05-09 13:30 ` Paolo Bonzini
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=ab3b2d59-109c-43d4-f97b-1c8ee1ee1f2c@redhat.com \
--to=pbonzini@redhat.com \
--cc=afaria@redhat.com \
--cc=eblake@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).