From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Linux Trace Kernel <linux-trace-kernel@vger.kernel.org>,
bpf@vger.kernel.org,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Mark Rutland <mark.rutland@arm.com>,
Peter Zijlstra <peterz@infradead.org>,
Namhyung Kim <namhyung@kernel.org>,
Takaya Saeki <takayas@google.com>,
Douglas Raillard <douglas.raillard@arm.com>,
Tom Zanussi <zanussi@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ian Rogers <irogers@google.com>, Jiri Olsa <olsajiri@gmail.com>
Subject: Re: [PATCH v4] tracing/probes: Allow use of BTF names to dereference pointers
Date: Wed, 20 May 2026 00:26:40 +0900 [thread overview]
Message-ID: <20260520002640.d372bd044ceba9364b1f168f@kernel.org> (raw)
In-Reply-To: <20260519083128.5795c6af@gandalf.local.home>
On Tue, 19 May 2026 08:31:28 -0400
Steven Rostedt <rostedt@goodmis.org> wrote:
> >
> > To access @data, simple casting does not work. Thus we need a
> > new syntax:
> >
> > (STRUCT)(PTR,ASSIGN)->FIELD
> >
> > So the above case, we can do:
> >
> > data=(foo)(foo_list,list)->data
>
> Hmm, it may be better to make it one parenthesis?
>
> (STRUCT,PTR,ASSIGN)->FIELD
>
> data=(foo,foo_list,list)->data
OK, but I don't like this 3 parameters conversion. I want to
make it a kind of type casting with an option.
(STRUCT,ASSIGN)PTR->FIELD
data=(foo,list)foo_list->data
The second parenthesis will be eventually needed for nested casting,
for example, in above case, if the data is a pointer to another data
structure:
struct bar {
int value;
...
};
value=(bar)((foo,list)foo_list->data)->value
>
> That would make it easier to differentiate between a simple "typecast" and
> a container_of() by checking if the content between the parenthesis has a
> comma.
>
> Maybe even reorder it to:
>
> (PTR,STRUCT,ASSIGN)->FIELD
>
> data=(foo_list,foo,list)->data
>
> to match the order of container_of():
>
> data = container_of(foo_list, struct foo, list)->data;
>
> ?
This doesn't seem to conform to the rule here of using parentheses for
type casting, so I personally don't like it.
> > > diff --git a/kernel/trace/trace_probe.c b/kernel/trace/trace_probe.c
> > > index e0d3a0da26af..b0829eb1cb52 100644
> > > --- a/kernel/trace/trace_probe.c
> > > +++ b/kernel/trace/trace_probe.c
> > > @@ -464,6 +464,26 @@ static const char *fetch_type_from_btf_type(struct btf *btf,
> > > return NULL;
> > > }
> > >
> > > +static int query_btf_struct(const char *sname, struct traceprobe_parse_context *ctx)
> > > +{
> > > + int id;
> > > +
> > > + if (!ctx->btf) {
> > > + struct btf *btf;
> >
> > This needs an empty line here.
>
> Sure.
>
> For conditional blocks, I don't always add a newline, but this is your code
> and I'll follow your suggestions.
Ah, this is just for fixing checkpatch.pl warning :-)
>
> >
> > > + id = bpf_find_btf_id(sname, BTF_KIND_STRUCT, &btf);
> > > + if (id < 0)
> > > + return -EINVAL;
> >
> > Why don't you return id (it has corresponding errno)?
>
> Because I forgot to ;-)
>
> >
> > > + ctx->btf = btf;
> > > + } else {
> > > + id = btf_find_by_name_kind(ctx->btf, sname, BTF_KIND_STRUCT);
> > > + if (id < 0)
> > > + return -EINVAL;
> >
> > Ditto.
> >
> > > + }
> > > +
> > > + ctx->last_struct = btf_type_by_id(ctx->btf, id);
> > > + return 0;
> > > +}
> > > +
> > > static int query_btf_context(struct traceprobe_parse_context *ctx)
> > > {
> > > const struct btf_param *param;
> > > @@ -471,12 +491,12 @@ static int query_btf_context(struct traceprobe_parse_context *ctx)
> > > struct btf *btf;
> > > s32 nr;
> > >
> > > - if (ctx->btf)
> > > - return 0;
> > > -
> > > if (!ctx->funcname)
> > > return -EINVAL;
> > >
> > > + if (ctx->btf)
> > > + return 0;
> > > +
> >
> > Could you tell me why this order is changed?
> > I think this type casting will allow us to skip checking funcname
> > because btf context is already specified.
>
> I wanted this to fail if btf was already set but funcname wasn't, because
> this should only be called for functions.
Hmm, OK. Then, can you make a separate patch for this?
>
> >
> > Ah, BTW, we may need to use a special struct btf* for type
> > casting. If the target function is in a module and the
> > casting type is defined in vmlinux, those are stored in
> > the different places...
>
> OK, I'll make a separate btf for it then. I'll have to make sure the btf
> used for parsing knows which one to use. Shouldn't be too hard if we check
> for the STRUCT flag in the ctx->flags.
Yeah, and personally, I think that flag should be the TYPECAST flag.
Thank you!
--
Masami Hiramatsu (Google) <mhiramat@kernel.org>
next prev parent reply other threads:[~2026-05-19 15:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-19 3:23 [PATCH v4] tracing/probes: Allow use of BTF names to dereference pointers Steven Rostedt
2026-05-19 9:34 ` kernel test robot
2026-05-19 9:53 ` Masami Hiramatsu
2026-05-19 12:31 ` Steven Rostedt
2026-05-19 15:26 ` Masami Hiramatsu [this message]
2026-05-19 16:28 ` Steven Rostedt
2026-05-19 16:38 ` Steven Rostedt
2026-05-19 10:10 ` kernel test robot
[not found] ` <20260519040928.458C4C2BCB3@smtp.kernel.org>
2026-05-19 12:36 ` Steven Rostedt
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=20260520002640.d372bd044ceba9364b1f168f@kernel.org \
--to=mhiramat@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=bpf@vger.kernel.org \
--cc=douglas.raillard@arm.com \
--cc=irogers@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mathieu.desnoyers@efficios.com \
--cc=namhyung@kernel.org \
--cc=olsajiri@gmail.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=takayas@google.com \
--cc=tglx@linutronix.de \
--cc=zanussi@kernel.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