Building the Linux kernel with Clang and LLVM
 help / color / mirror / Atom feed
From: Vineet Gupta <vineet.gupta@linux.dev>
To: Chris Down <chris@chrisdown.name>
Cc: dennis@kernel.org, tj@kernel.org, cl@gentwo.org,
	peterz@infradead.org, mingo@redhat.com, will@kernel.org,
	boqun@kernel.org, longman@redhat.com, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org, bpf@vger.kernel.org,
	ast@kernel.org, andrii@kernel.org, daniel@iogearbox.net,
	acme@kernel.org, yonghong.song@linux.dev, eddyz87@gmail.com,
	martin.lau@linux.dev, nathan@kernel.org, ndesaulniers@google.com,
	morbo@google.com, justinstitt@google.com, llvm@lists.linux.dev
Subject: Re: [RFC PATCH 2/2] local_lock: do not put btf_type_tag on the lock guard type
Date: Mon, 16 Nov 2026 13:49:02 -0800	[thread overview]
Message-ID: <2e6d98fe-527f-4188-bca0-c9db1ad92bce@linux.dev> (raw)
In-Reply-To: <20261113115810.cd33f9ed58c02dd9@chrisdown.name>

On 11/13/26 11:58 AM, Chris Down wrote:
> Hi Vineet,
>
> Vineet Gupta <vineet.gupta@linux.dev> writes:
>> 	typedef local_lock_t __seg_gs
>> 	__attribute__((btf_type_tag("percpu"))) lock_local_lock_t;
>>
>> 	typedef struct { local_lock_t __seg_gs
>> 	__attribute__((btf_type_tag("percpu"))) *lock; } class_local_lock_t;
>>
>> Both put the tag on local_lock_t, an aggregate: the first on a typedef of
>> it, the second on the pointee of the guard's member.
> The typedef is the aggregate case, and it's the only one of the two that
> GCC warns about. But the second one is just the "T __percpu *p" spelling
> that 1/2 keeps the tag for. _T->lock really is a pointer to per-cpu memory,
> since local_lock() passes it to this_cpu_ptr(). So the tag is correct
> there. This patch drops it from the guard's lock member and the
> constructor's argument as well, not only from the typedef. I think it
> should keep the tag on those two and only drop it from the typedef.

Yes you are right, the patch conflated them. And although the warning is 
same as in patch 1, there typedef is actually involved


>> Every variant of an
>> aggregate shares one DIE, so there is nowhere to record it, exactly as for
>> DECLARE_PER_CPU() of a struct. clang writes the annotation into DWARF
>> without complaint, but pahole does not translate it from that position,
>> so with today's toolchains it reaches BTF from neither compiler.
> That's true of the typedef, but not of the member. With clang 23 and
> pahole 1.32 the lock member comes out as PTR -> TYPE_TAG 'percpu' ->
> local_lock_t, the same as any other per-cpu pointer.

Yep it was wrong for the member. My config was lacking 
CONFIG_CONTEXT_ANALYSIS_TEST and hence it missed this part.

> For the typedef, clang 23 puts the annotation on the typedef's own DIE, as
> you say, so there is somewhere to record it. It's only pahole that doesn't
> pick it up yet. You also mentioned GCC patches for type tags on typedefs
> in the pahole thread [0]. Once those land, does this warning go away?

Correct, although [0] you referred to is a different, likely won't fix.
The fix you have in mind is PR125888 [1] and the patches are here [2]
This addresses the For BTF, as you say, pahole doesn't convert 
annotation from a typedef DIE so the

>> Unlike the per-cpu declarations this changes no BTF at all. A tag in that
>> position was never recorded, so there is nothing to remove, and the one
>> percpu TYPE_TAG that does reach a local_lock type comes from those casts,
>> which keep it. An x86 defconfig built with clang is identical with and
>> without this patch: 152551 BTF types and a 6828300 byte .BTF either way,
>> and .text is unchanged. The patch removes a GCC diagnostic and no more.
> The defconfig BTF only stays the same because nothing in a defconfig uses
> these guards. lib/test_context-analysis.c is the only user in the tree.
> With CONFIG_CONTEXT_ANALYSIS_TEST=y, class_local_lock_t,
> class_local_lock_irq_t, class_local_lock_irqsave_t and
> class_local_lock_nested_bh_t all lose the percpu tag on lock with this
> patch applied.

Yep I was missing that.

> Nothing in BPF looks at those types today, so this doesn't break anything.
> But it does remove correct annotations to get rid of a warning that is
> only ever caused by the typedef itself. When the guards were added, the
> type was only ever used as _type *. The typedef came later with
> 3931d4b98039 ("cleanup: Basic compatibility with context analysis"). If
> GCC isn't going to accept the tag on a typedef, could this be limited to
> that typedef in cleanup.h instead, so the guard's pointer keeps its tag?
> As far as I can see, lock_##_name##_t is only ever used through a
> pointer, in DECLARE_LOCK_GUARD_1_ATTRS().

I think GCC supporting them seems like a reasonable ask - fixes have 
been posted, lets see.

But to recap, I will drop this patch since it only needs to handle the 
warning which can't be fixed in source and relies on the GCC fix.

The point of this series was to do any needed kernel source changes 
which can't be addresses in GCC.
e.g. PR128480 [3] was deemed invalid/wont-fix on GCC side.

> [0] https://lore.kernel.org/r/252c53f3-3f06-40f4-9cd3-795eb298687c@linux.dev

[1] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=125888
[2] 
https://inbox.sourceware.org/gcc-patches/20261112191815.884167-1-vineet.gupta@linux.dev/
[3] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=128480

Thanks again for chiming in.
-Vineet

      reply	other threads:[~2026-11-16 21:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-10  1:22 [RFC PATCH 0/2] percpu, local_lock: drop btf_type_tag where no compiler records it Vineet Gupta
2026-11-10  1:22 ` [RFC PATCH 1/2] percpu: do not put btf_type_tag on per-cpu variable declarations Vineet Gupta
2026-11-13 19:58   ` Chris Down
2026-11-13 22:36     ` Vineet Gupta
2026-11-10  1:22 ` [RFC PATCH 2/2] local_lock: do not put btf_type_tag on the lock guard type Vineet Gupta
2026-11-13 19:58   ` Chris Down
2026-11-16 21:49     ` Vineet Gupta [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=2e6d98fe-527f-4188-bca0-c9db1ad92bce@linux.dev \
    --to=vineet.gupta@linux.dev \
    --cc=acme@kernel.org \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=boqun@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=chris@chrisdown.name \
    --cc=cl@gentwo.org \
    --cc=daniel@iogearbox.net \
    --cc=dennis@kernel.org \
    --cc=eddyz87@gmail.com \
    --cc=justinstitt@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=llvm@lists.linux.dev \
    --cc=longman@redhat.com \
    --cc=martin.lau@linux.dev \
    --cc=mingo@redhat.com \
    --cc=morbo@google.com \
    --cc=nathan@kernel.org \
    --cc=ndesaulniers@google.com \
    --cc=peterz@infradead.org \
    --cc=tj@kernel.org \
    --cc=will@kernel.org \
    --cc=yonghong.song@linux.dev \
    /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