From: Thomas Huth <thuth@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Peter Maydell" <peter.maydell@linaro.org>,
"Kevin Wolf" <kwolf@redhat.com>
Cc: qemu-block@nongnu.org, qemu-devel@nongnu.org,
Emanuele Giuseppe Esposito <eesposit@redhat.com>
Subject: Re: [PULL 00/29] Block layer patches
Date: Mon, 27 Feb 2023 10:12:01 +0100 [thread overview]
Message-ID: <ea176722-9dee-0df6-edf2-b8ff8e1193ba@redhat.com> (raw)
In-Reply-To: <d6280636-d40f-a79d-ead0-4b94a0628f10@linaro.org>
On 24/02/2023 22.35, Philippe Mathieu-Daudé wrote:
> Hi,
>
> On 24/2/23 19:50, Peter Maydell wrote:
>> On Thu, 23 Feb 2023 at 18:51, Kevin Wolf <kwolf@redhat.com> wrote:
>>>
>>> The following changes since commit 79b677d658d3d35e1e776826ac4abb28cdce69b8:
>>>
>>> Merge tag 'net-pull-request' of https://github.com/jasowang/qemu into
>>> staging (2023-02-21 11:28:31 +0000)
>>>
>>> are available in the Git repository at:
>>>
>>> https://repo.or.cz/qemu/kevin.git tags/for-upstream
>>>
>>> for you to fetch changes up to 0f385a2420d2c3f8ae7ed65fbe2712027664059e:
>>>
>>> block/rbd: Add support for layered encryption (2023-02-23 19:49:35 +0100)
>>>
>>> ----------------------------------------------------------------
>>> Block layer patches
>>>
>>> - Lock the graph, part 2 (BlockDriver callbacks)
>>> - virtio-scsi: fix SCSIDevice hot unplug with IOThread
>>> - rbd: Add support for layered encryption
>>>
>>> ----------------------------------------------------------------
>>
>>
>> Applied, thanks.
>
> Configuring with --extra-cflags=-ggdb, on
>
> C compiler for the host machine: clang (clang 14.0.0 "Apple clang version
> 14.0.0 (clang-1400.0.29.202)")
> C linker for the host machine: clang ld64 820.1
> Host machine cpu family: aarch64
> Host machine cpu: aarch64
> ...
> CFLAGS : -ggdb -g -O2
>
> I'm getting:
>
> ../../block/io.c:182:38: warning: reading variable 'bdrv_aio_preadv'
> requires holding mutex 'graph_lock' [-Wthread-safety-analysis]
> drv->bdrv_aio_preadv ||
> ^
> ../../block/io.c:997:14: warning: reading variable 'bdrv_aio_preadv'
> requires holding mutex 'graph_lock' [-Wthread-safety-analysis]
> if (drv->bdrv_aio_preadv) {
> ^
> ../../block/io.c:1003:20: warning: reading variable 'bdrv_aio_preadv'
> requires holding mutex 'graph_lock' [-Wthread-safety-analysis]
> acb = drv->bdrv_aio_preadv(bs, offset, bytes, qiov, flags,
> ^
> ../../block/io.c:1076:14: warning: reading variable 'bdrv_aio_pwritev'
> requires holding mutex 'graph_lock' [-Wthread-safety-analysis]
> if (drv->bdrv_aio_pwritev) {
> ^
> ../../block/io.c:1082:20: warning: reading variable 'bdrv_aio_pwritev'
> requires holding mutex 'graph_lock' [-Wthread-safety-analysis]
> acb = drv->bdrv_aio_pwritev(bs, offset, bytes, qiov, flags,
> ^
> ../../block/io.c:2899:25: warning: reading variable 'bdrv_aio_flush'
> requires holding mutex 'graph_lock' [-Wthread-safety-analysis]
> } else if (bs->drv->bdrv_aio_flush) {
> ^
> ../../block/io.c:2905:24: warning: reading variable 'bdrv_aio_flush'
> requires holding mutex 'graph_lock' [-Wthread-safety-analysis]
> acb = bs->drv->bdrv_aio_flush(bs, bdrv_co_io_em_complete, &co);
> ^
> ../../block/io.c:2991:49: warning: reading variable 'bdrv_aio_pdiscard'
> requires holding mutex 'graph_lock' [-Wthread-safety-analysis]
> if (!bs->drv->bdrv_co_pdiscard && !bs->drv->bdrv_aio_pdiscard) {
> ^
> ../../block/io.c:3058:28: warning: reading variable 'bdrv_aio_pdiscard'
> requires holding mutex 'graph_lock' [-Wthread-safety-analysis]
> acb = bs->drv->bdrv_aio_pdiscard(bs, offset, num,
> ^
> ../../block/io.c:3094:24: warning: reading variable 'bdrv_aio_ioctl'
> requires holding mutex 'graph_lock' [-Wthread-safety-analysis]
> if (!drv || (!drv->bdrv_aio_ioctl && !drv->bdrv_co_ioctl)) {
> ^
> ../../block/io.c:3102:20: warning: reading variable 'bdrv_aio_ioctl'
> requires holding mutex 'graph_lock' [-Wthread-safety-analysis]
> acb = drv->bdrv_aio_ioctl(bs, req, buf, bdrv_co_io_em_complete, &co);
> ^
> 11 warnings generated.
This can also reproduced in the gitlab-ci:
https://gitlab.com/thuth/qemu/-/jobs/3837884040#L2862
Peter, in case you also have a github account, could you maybe enable the
Cirrus-CI for your gitlab repo like it is explained here:
.gitlab-ci.d/cirrus/README.rst
?
Thanks,
Thomas
next prev parent reply other threads:[~2023-02-27 9:12 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-23 18:51 [PULL 00/29] Block layer patches Kevin Wolf
2023-02-23 18:51 ` [PULL 01/29] block: Make bdrv_can_set_read_only() static Kevin Wolf
2023-02-23 18:51 ` [PULL 02/29] mirror: Fix access of uninitialised fields during start Kevin Wolf
2023-02-23 18:51 ` [PULL 03/29] block: Mark bdrv_co_truncate() and callers GRAPH_RDLOCK Kevin Wolf
2023-02-23 18:51 ` [PULL 04/29] block: Mark bdrv_co_block_status() " Kevin Wolf
2023-02-23 18:51 ` [PULL 05/29] block: Mark bdrv_co_ioctl() " Kevin Wolf
2023-02-23 18:51 ` [PULL 06/29] block/qed: add missing graph rdlock in qed_need_check_timer_entry Kevin Wolf
2023-02-23 18:51 ` [PULL 07/29] block: Mark bdrv_co_flush() and callers GRAPH_RDLOCK Kevin Wolf
2023-02-23 18:51 ` [PULL 08/29] block: Mark bdrv_co_pdiscard() " Kevin Wolf
2023-02-23 18:51 ` [PULL 09/29] block: Mark bdrv_co_pwrite_zeroes() " Kevin Wolf
2023-02-23 18:51 ` [PULL 10/29] block: Mark read/write in block/io.c GRAPH_RDLOCK Kevin Wolf
2023-02-23 18:51 ` [PULL 11/29] block: Mark public read/write functions GRAPH_RDLOCK Kevin Wolf
2023-02-23 18:51 ` [PULL 12/29] block: Mark bdrv_co_pwrite_sync() and callers GRAPH_RDLOCK Kevin Wolf
2023-02-23 18:51 ` [PULL 13/29] block: Mark bdrv_co_do_pwrite_zeroes() GRAPH_RDLOCK Kevin Wolf
2023-02-23 18:51 ` [PULL 14/29] block: Mark bdrv_co_copy_range() GRAPH_RDLOCK Kevin Wolf
2023-02-23 18:51 ` [PULL 15/29] block: Mark preadv_snapshot/snapshot_block_status GRAPH_RDLOCK Kevin Wolf
2023-02-23 18:51 ` [PULL 16/29] block: Mark bdrv_co_create() and callers GRAPH_RDLOCK Kevin Wolf
2023-02-23 18:51 ` [PULL 17/29] block: Mark bdrv_co_io_(un)plug() " Kevin Wolf
2023-02-23 18:51 ` [PULL 18/29] block: Mark bdrv_co_is_inserted() " Kevin Wolf
2023-02-23 18:51 ` [PULL 19/29] block: Mark bdrv_co_eject/lock_medium() " Kevin Wolf
2023-02-23 18:51 ` [PULL 20/29] block: Mark bdrv_(un)register_buf() GRAPH_RDLOCK Kevin Wolf
2023-02-23 18:51 ` [PULL 21/29] block: Mark bdrv_co_delete_file() and callers GRAPH_RDLOCK Kevin Wolf
2023-02-23 18:51 ` [PULL 22/29] block: Mark bdrv_*_dirty_bitmap() " Kevin Wolf
2023-02-23 18:51 ` [PULL 23/29] block: Mark bdrv_co_refresh_total_sectors() " Kevin Wolf
2023-02-23 18:51 ` [PULL 24/29] scsi: protect req->aiocb with AioContext lock Kevin Wolf
2023-02-23 18:51 ` [PULL 25/29] dma-helpers: prevent dma_blk_cb() vs dma_aio_cancel() race Kevin Wolf
2023-02-23 18:51 ` [PULL 26/29] virtio-scsi: reset SCSI devices from main loop thread Kevin Wolf
2023-02-23 18:51 ` [PULL 27/29] block/rbd: Remove redundant stack variable passphrase_len Kevin Wolf
2023-02-23 18:51 ` [PULL 28/29] block/rbd: Add luks-any encryption opening option Kevin Wolf
2023-02-23 18:51 ` [PULL 29/29] block/rbd: Add support for layered encryption Kevin Wolf
2023-02-24 18:50 ` [PULL 00/29] Block layer patches Peter Maydell
2023-02-24 21:35 ` Philippe Mathieu-Daudé
2023-02-27 9:12 ` Thomas Huth [this message]
2023-02-27 11:22 ` Peter Maydell
-- strict thread matches above, loose matches on Subject: below --
2020-03-06 17:14 Kevin Wolf
2020-03-06 19:16 ` no-reply
2020-03-06 19:26 ` Peter Maydell
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=ea176722-9dee-0df6-edf2-b8ff8e1193ba@redhat.com \
--to=thuth@redhat.com \
--cc=eesposit@redhat.com \
--cc=kwolf@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@linaro.org \
--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).