From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
To: sashiko-reviews@lists.linux.dev
Cc: sashiko-bot@kernel.org, linux-trace-kernel@vger.kernel.org,
linux-perf-users@vger.kernel.org
Subject: Re: [PATCH v14 02/14] tracing/probes: Fix BTF kflag check for anonymous struct member access
Date: Mon, 31 Aug 2026 10:24:37 +0900 [thread overview]
Message-ID: <20260831102437.7af7f7a28a8f34ff79655e07@kernel.org> (raw)
In-Reply-To: <20260830143859.D56991F00A3D@smtp.kernel.org>
On Sun, 30 Aug 2026 14:38:59 +0000
sashiko-bot@kernel.org wrote:
> Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
>
> Pre-existing issues:
> - [High] Unnamed bitfields break nested anonymous struct resolution in btf_find_struct_member().
> --
>
> commit 20a606aa6d4e155be5a531c5d52d78c34205c0b4
> Author: Masami Hiramatsu (Google) <mhiramat@kernel.org>
>
> tracing/probes: Fix BTF kflag check for anonymous struct member access
>
> This commit fixes how BTF kflags are checked when traversing nested
> anonymous structures and unions in btf_find_struct_member() by using
> the actual containing type.
>
> > diff --git a/kernel/trace/trace_btf.c b/kernel/trace/trace_btf.c
> > --- a/kernel/trace/trace_btf.c
> > +++ b/kernel/trace/trace_btf.c
>
> [ ... ]
>
> > @@ -91,17 +92,23 @@ const struct btf_member *btf_find_struct_member(struct btf *btf,
> > for_each_member(i, type, member) {
> > if (!member->name_off) {
> > /* Anonymous union/struct: push it for later use */
> > + u32 m_off = btf_type_kflag(type) ?
> > + BTF_MEMBER_BIT_OFFSET(member->offset) :
> > + member->offset;
> > +
> > if (btf_type_skip_modifiers(btf, member->type, &tid) &&
> > top < BTF_ANON_STACK_MAX) {
> > anon_stack[top].tid = tid;
> > anon_stack[top++].offset =
> > - cur_offset + member->offset;
> > + cur_offset + m_off;
> > }
> > } else {
>
> [Severity: High]
> This isn't a bug introduced by this patch, but is it possible for unnamed
> bitfields to break nested anonymous struct resolution here?
>
Oops, unnamed bitfield.... I didn't expected that.
> Since unnamed bitfields (like int : 5) also have name_off == 0, they get
> pushed onto anon_stack alongside actual anonymous structs.
OK, I got it. This function only expects anonymous struct/union, not
anonymous bitfield.
>
> Because anon_stack is processed in LIFO order, an unnamed bitfield defined
> after an anonymous struct will be popped first. When it is popped at the top
> of btf_find_struct_member():
>
> retry:
> if (!btf_type_is_struct(type)) {
> member = ERR_PTR(-EINVAL);
> goto out;
> }
>
> Does this cause the scalar type check to fail and abort the entire search,
> preventing the earlier anonymous struct from ever being searched?
Yeah, this is wrong. it should check this is the last anon_stack entry
and retry. Maybe we should make it a loop.
Thanks!
>
> > name = btf_name_by_offset(btf, member->name_off);
> > if (name && !strcmp(member_name, name)) {
> > if (anon_offset)
> > *anon_offset = cur_offset;
>
> --
> Sashiko AI review · https://sashiko.dev/#/patchset/178810001186.64882.2161016469449127450.stgit@devnote2?part=2
--
Masami Hiramatsu (Google) <mhiramat@kernel.org>
next prev parent reply other threads:[~2026-08-31 1:24 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-30 14:26 [PATCH v14 00/14] tracing: wprobe: x86: Add wprobe for watchpoint Masami Hiramatsu (Google)
2026-08-30 14:27 ` [PATCH v14 01/14] x86/mce: Fix hardware debug register corruption on task migration Masami Hiramatsu (Google)
2026-08-30 14:40 ` sashiko-bot
2026-08-30 14:27 ` [PATCH v14 02/14] tracing/probes: Fix BTF kflag check for anonymous struct member access Masami Hiramatsu (Google)
2026-08-30 14:38 ` sashiko-bot
2026-08-31 1:24 ` Masami Hiramatsu [this message]
2026-08-30 14:27 ` [PATCH v14 03/14] kprobes: Protect kprobe_blacklist with RCU Masami Hiramatsu (Google)
2026-08-30 14:33 ` sashiko-bot
2026-09-02 1:30 ` Masami Hiramatsu
2026-08-30 14:27 ` [PATCH v14 04/14] x86/hw_breakpoints: Make DR7 updates NMI safe Masami Hiramatsu (Google)
2026-08-30 14:45 ` sashiko-bot
2026-08-30 14:27 ` [PATCH v14 05/14] x86/hw_breakpoints: Add arch_modify_local_hw_breakpoint_addr() API Masami Hiramatsu (Google)
2026-08-30 14:38 ` sashiko-bot
2026-08-30 14:27 ` [PATCH v14 06/14] HWBP: Add modify_local_hw_breakpoint_addr() API Masami Hiramatsu (Google)
2026-08-30 14:40 ` sashiko-bot
2026-08-30 14:28 ` [PATCH v14 07/14] tracing/wprobe: Add wprobe (watchpoint probe) trace event support Masami Hiramatsu (Google)
2026-08-30 14:42 ` sashiko-bot
2026-08-30 14:28 ` [PATCH v14 08/14] x86: hw_breakpoint: Add a kconfig to clarify when a breakpoint fires Masami Hiramatsu (Google)
2026-08-30 14:33 ` sashiko-bot
2026-08-30 14:28 ` [PATCH v14 09/14] selftests: tracing: Add a basic testcase for wprobe Masami Hiramatsu (Google)
2026-08-30 14:34 ` sashiko-bot
2026-08-30 14:28 ` [PATCH v14 10/14] selftests: tracing: Add syntax " Masami Hiramatsu (Google)
2026-08-30 14:37 ` sashiko-bot
2026-08-30 14:28 ` [PATCH v14 11/14] tracing/wprobe: Add set_wprobe and clear_wprobe event triggers Masami Hiramatsu (Google)
2026-08-30 14:52 ` sashiko-bot
2026-08-30 14:29 ` [PATCH v14 12/14] selftests: ftrace: Add wprobe trigger testcase Masami Hiramatsu (Google)
2026-08-30 14:44 ` sashiko-bot
2026-08-30 14:29 ` [PATCH v14 13/14] tracing/wprobe: Support BTF typecast in fetchargs Masami Hiramatsu (Google)
2026-08-30 14:44 ` sashiko-bot
2026-08-30 14:29 ` [PATCH v14 14/14] tracing/wprobe: Support BTF struct offset resolution in set_wprobe trigger Masami Hiramatsu (Google)
2026-08-30 14:46 ` sashiko-bot
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=20260831102437.7af7f7a28a8f34ff79655e07@kernel.org \
--to=mhiramat@kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=sashiko-bot@kernel.org \
--cc=sashiko-reviews@lists.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