From: Joe Perches <joe@perches.com>
To: Vincent Donnefort <vdonnefort@google.com>,
apw@canonical.com, akpm@linux-foundation.org
Cc: elver@google.com, linux-kernel@vger.kernel.org, kernel-team@android.com
Subject: Re: [PATCH v1] checkpatch: Add context-analysis attributes
Date: Thu, 12 Nov 2026 19:32:14 -0800 [thread overview]
Message-ID: <6dfeacb309d58f153c1cd701cd31a587151e9070.camel@perches.com> (raw)
In-Reply-To: <20261112151203.3129005-1-vdonnefort@google.com>
On Thu, 2026-11-12 at 15:12 +0000, Vincent Donnefort wrote:
> Checkpatch doesn't know about the context analysis attributes and
> misparses annotated declarations (e.g. mistaking __guarded_by() fields
> for extern prototype). Add them to the known attributes list.
Nak.
> diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
[]
> @@ -526,6 +526,25 @@ our $InitAttributeData = qr{$InitAttributePrefix(?:initdata\b)};
> our $InitAttributeConst = qr{$InitAttributePrefix(?:initconst\b)};
> our $InitAttributeInit = qr{$InitAttributePrefix(?:init\b)};
> our $InitAttribute = qr{$InitAttributeData|$InitAttributeConst|$InitAttributeInit};
> +our $ContextAnalysis = qr{
Are all of these from include/linux/compiler-context-analysis.h ?
> + __guarded_by\b|
__guarded_by takes an argument so it should be
__guarded_by\s*\(.*\)
like the __aligned use below in $Attribute
> + __pt_guarded_by\b|
And all the rest of these entries that take arguments need to add
that same '\s*\(.*\)'
and it'll be fragile besides, multiline uses likely won't work,
any use that has another internal () pair won't work, etc...
> + __rcu_guarded\b|
> + __must_hold\b|
> + __must_hold_shared\b|
> + __must_not_hold\b|
> + __acquires\b|
> + __acquires_shared\b|
> + __cond_acquires\b|
> + __cond_acquires_shared\b|
> + __releases\b|
> + __releases_shared\b|
> + __cond_releases\b|
> + __no_context_analysis\b|
> + __context_unsafe\b|
> + __acquires_ret\b|
> + __acquires_shared_ret\b
> + }x;
>
> # Notes to $Attribute:
> # We need \b after 'init' otherwise 'initconst' will cause a false positive in a check
> @@ -551,6 +570,7 @@ our $Attribute = qr{
> __ro_after_init|
> __kprobes|
> $InitAttribute|
> + $ContextAnalysis|
> __aligned\s*\(.*\)|
> ____cacheline_aligned|
> ____cacheline_aligned_in_smp|
>
> base-commit: 6628e7d4c6b25c8d18f1345e3a20d21829aae7e4
prev parent reply other threads:[~2026-11-13 3:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-12 15:12 Vincent Donnefort
2026-11-12 15:23 ` Marco Elver
2026-11-13 3:32 ` Joe Perches [this message]
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=6dfeacb309d58f153c1cd701cd31a587151e9070.camel@perches.com \
--to=joe@perches.com \
--cc=akpm@linux-foundation.org \
--cc=apw@canonical.com \
--cc=elver@google.com \
--cc=kernel-team@android.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vdonnefort@google.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®