Linux block layer
 help / color / mirror / Atom feed
From: Bart Van Assche <bvanassche@acm.org>
To: Marco Elver <elver@google.com>, Peter Zijlstra <peterz@infradead.org>
Cc: Jens Axboe <axboe@kernel.dk>,
	linux-block@vger.kernel.org, Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH v4 02/12] block/bdev: Annotate the blk_holder_ops callback functions
Date: Tue, 12 May 2026 12:28:50 -0700	[thread overview]
Message-ID: <56a1f905-2348-483b-a79e-5b3ebbd3482d@acm.org> (raw)
In-Reply-To: <CANpmjNNMDY=gB23ejdDYZg5yYduup_iXE1FAWC-fghr2od7Hwg@mail.gmail.com>

On 5/11/26 3:19 PM, Marco Elver wrote:
> On Mon, 11 May 2026 at 18:31, Bart Van Assche <bvanassche@acm.org> wrote:
>>
>> The four callback functions in blk_holder_ops all release the
>> bd_holder_lock. Annotate these functions accordingly.
>>
>> Signed-off-by: Bart Van Assche <bvanassche@acm.org>
> 
> Because of this change we'll need clang 23, or you add:
> 
> CONTEXT_ANALYSIS := $(call clang-min-version, 230000)
> 
> .. although anything else that includes blkdev.h that has
> CONTEXT_ANALYSIS := y, but is compiled with clang 22 will break.
> 
> Would have been good to wait for clang 23 to be released (August this
> year) - although if we consider the next merge window + final release
> of Linux 7.2, it might get reasonably close to August.

Hi Marco,

How about detecting whether or not Clang supports context annotations
for function pointers, e.g. as follows?

diff --git a/init/Kconfig b/init/Kconfig
index 2937c4d308ae..61e592205179 100644
--- a/init/Kconfig
+++ b/init/Kconfig
@@ -32,6 +32,9 @@ config CLANG_VERSION
  	default $(cc-version) if CC_IS_CLANG
  	default 0

+config CC_CONTEXT_ANNOTATIONS_ON_FUNCTION_POINTERS
+	def_bool $(success, echo 'struct __attribute__((capability("m"))) m { 
}; struct a { void (*fp)(struct m* m) 
__attribute__((release_capability(m))); };' | $(CC) -x c - -c -Wall 
-Wextra -Werror -o /dev/null)
+
  config AS_IS_GNU
  	def_bool $(success,test "$(as-name)" = GNU)


Thanks,

Bart.

  reply	other threads:[~2026-05-12 19:28 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-11 16:30 [PATCH v4 00/12] Enable lock context analysis Bart Van Assche
2026-05-11 16:30 ` [PATCH v4 01/12] block: Annotate the queue limits functions Bart Van Assche
2026-05-11 16:30 ` [PATCH v4 02/12] block/bdev: Annotate the blk_holder_ops callback functions Bart Van Assche
2026-05-11 22:19   ` Marco Elver
2026-05-12 19:28     ` Bart Van Assche [this message]
2026-05-11 16:30 ` [PATCH v4 03/12] block/cgroup: Split blkg_conf_prep() Bart Van Assche
2026-05-11 16:30 ` [PATCH v4 04/12] block/cgroup: Split blkg_conf_exit() Bart Van Assche
2026-05-11 16:30 ` [PATCH v4 05/12] block/cgroup: Improve lock context annotations Bart Van Assche
2026-05-11 16:30 ` [PATCH v4 06/12] block/cgroup: Inline blkg_conf_{open,close}_bdev_frozen() Bart Van Assche
2026-05-11 16:30 ` [PATCH v4 07/12] block/crypto: Annotate the crypto functions Bart Van Assche
2026-05-11 16:30 ` [PATCH v4 08/12] block/blk-iocost: Add lock context annotations Bart Van Assche
2026-05-11 16:30 ` [PATCH v4 09/12] block/blk-mq-debugfs: Improve " Bart Van Assche
2026-05-11 16:30 ` [PATCH v4 10/12] block/kyber: Make the lock context annotations compatible with Clang Bart Van Assche
2026-05-11 16:30 ` [PATCH v4 11/12] block/mq-deadline: " Bart Van Assche
2026-05-11 16:30 ` [PATCH v4 12/12] block: Enable lock context analysis Bart Van Assche

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=56a1f905-2348-483b-a79e-5b3ebbd3482d@acm.org \
    --to=bvanassche@acm.org \
    --cc=axboe@kernel.dk \
    --cc=elver@google.com \
    --cc=hch@lst.de \
    --cc=linux-block@vger.kernel.org \
    --cc=peterz@infradead.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