All of lore.kernel.org
 help / color / mirror / Atom feed
From: Markus Armbruster <armbru@redhat.com>
To: Sam Li <faithilikerun@gmail.com>
Cc: qemu-devel@nongnu.org,  dmitry.fomichev@wdc.com,
	 qemu-block@nongnu.org, Kevin Wolf <kwolf@redhat.com>,
	 dlemoal@kernel.org,  hare@suse.de,
	 Hanna Reitz <hreitz@redhat.com>,
	 stefanha@redhat.com,  Eric Blake <eblake@redhat.com>
Subject: Re: [PATCH v6 0/4] Add full zoned storage emulation to qcow2 driver
Date: Thu, 30 Nov 2023 09:25:00 +0100	[thread overview]
Message-ID: <87leafejhf.fsf@pond.sub.org> (raw)
In-Reply-To: <20231127043703.49489-1-faithilikerun@gmail.com> (Sam Li's message of "Mon, 27 Nov 2023 12:36:59 +0800")

Clang reports

../block/qcow2.c:4066:5: error: mutex 'graph_lock' is not held on every path through here [-Werror,-Wthread-safety-analysis]
    blk_co_unref(blk);
    ^
../block/qcow2.c:3928:5: note: mutex acquired here
    bdrv_graph_co_rdlock();
    ^
../block/qcow2.c:4066:5: error: mutex 'graph_lock' is not held on every path through here [-Werror,-Wthread-safety-analysis]
    blk_co_unref(blk);
    ^
../block/qcow2.c:3928:5: note: mutex acquired here
    bdrv_graph_co_rdlock();
    ^
2 errors generated.



  parent reply	other threads:[~2023-11-30  8:25 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-27  4:36 [PATCH v6 0/4] Add full zoned storage emulation to qcow2 driver Sam Li
2023-11-27  4:37 ` [PATCH v6 1/4] docs/qcow2: add the zoned format feature Sam Li
2023-11-27  4:37 ` [PATCH v6 2/4] qcow2: add configurations for zoned format extension Sam Li
2023-11-30  8:40   ` Markus Armbruster
2023-12-17  0:30     ` Sam Li
2023-12-18 13:52       ` Markus Armbruster
2023-11-27  4:37 ` [PATCH v6 3/4] qcow2: add zoned emulation capability Sam Li
2023-11-27  7:53   ` Damien Le Moal
2023-11-27  4:37 ` [PATCH v6 4/4] iotests: test the zoned format feature for qcow2 file Sam Li
2023-11-30  8:25 ` Markus Armbruster [this message]
2023-12-17  1:22   ` [PATCH v6 0/4] Add full zoned storage emulation to qcow2 driver Sam Li

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=87leafejhf.fsf@pond.sub.org \
    --to=armbru@redhat.com \
    --cc=dlemoal@kernel.org \
    --cc=dmitry.fomichev@wdc.com \
    --cc=eblake@redhat.com \
    --cc=faithilikerun@gmail.com \
    --cc=hare@suse.de \
    --cc=hreitz@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.