mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
To: kylebot@openai.com
Cc: Masami Hiramatsu <mhiramat@kernel.org>,
	linux-trace-kernel@vger.kernel.org, linux-kernel@vger.kernel.org,
	rostedt@goodmis.org, outbounddisclosures@openai.com,
	stable@vger.kernel.org
Subject: Re: [PATCH] tracing/filters: Check perf permissions before resolving .function
Date: Wed, 07 Oct 2026 05:52:22 +0000	[thread overview]
Message-ID: <20261007055225.32DDA1F0089B@smtp.kernel.org> (raw)
In-Reply-To: <asXAxf0edslJI-Ge@com-75606>

On Tue, 06 Oct 2026 20:47:17 -0700, Kyle Zeng <kylebot@openai.com> wrote:
> On Wed, Oct 07, 2026 at 03:44:20AM +0000, Masami Hiramatsu wrote:
> > On Tue, 06 Oct 2026 15:51:12 -0700, Kyle Zeng <kylebot@openai.com> wrote:
> > > perf_trace_event_perm() allows tracepoint counters that do not request
> > > PERF_SAMPLE_RAW without raw tracepoint permissions. A self-targeted,
> > > disabled event with exclude_kernel=1 can therefore reach the filter
> > > compiler even at perf_event_paranoid=2.
> > >
> > > The .function suffix accepts any field of sizeof(long) and resolves its
> > > operand through kallsyms_lookup_name() and kallsyms_lookup_size_offset().
> > > The success or failure of a numeric filter discloses whether an address
> > > belongs to a known kernel symbol range. On x86-64 this can be used to
> > > recover the randomized kernel image base. A named filter also exposes
> > > the resolved symbol range through the counter when the tracepoint field
> > > is controlled by the caller, as with a syscall argument.
> > >
> > > Pass the filter's perf origin to the predicate parser and require
> > > perf_allow_tracepoint() before resolving a .function operand. This uses
> > > the same sysctl, initial-namespace capability and LSM policy as raw
> > > tracepoint access, and closes both the numeric and named-symbol oracles.
> > > Do not change ordinary perf counting filters or filters created through
> > > the separately controlled tracefs interfaces.
> > 
> > Good catch!
> > 
> > >
> > > Fixes: e6745a4da964 ("tracing: Add a way to filter function addresses to function names")
> > > Cc: stable@vger.kernel.org
> > > Assisted-by: Codex:gpt-6-astra
> > 
> > nit: This should be 
> > 
> > Assisted-by: LLM
>
> Didn't know there was a change of convention. Should I send in a v2 or
> it will be picked up automatically?

We can change the tag when picking up, so you don't need to resend it only
for tag update. But for this patch, please update according to Sashiko's
comment.

 https://lore.kernel.org/all/sashiko-outbox-162502@kernel.org/

Thanks,

>
> Thanks,
> Kyle
>
> > 
> > > Signed-off-by: Kyle Zeng <kylebot@openai.com>
> > 
> > Reviewed-by: Masami Hiramatsu (Google) <mhiramat@kernel.org>
> > 
> > Thanks!
> > 
> > 
> > -- 
> > Masami Hiramatsu (Google) <mhiramat@kernel.org>

-- 
Masami Hiramatsu (Google) <mhiramat@kernel.org>

  reply	other threads:[~2026-10-07  5:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-06 22:51 Kyle Zeng
2026-10-07  3:44 ` Masami Hiramatsu
2026-10-07  3:47   ` Kyle Zeng
2026-10-07  5:52     ` Masami Hiramatsu [this message]
2026-10-07  5:56       ` Kyle Zeng

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=20261007055225.32DDA1F0089B@smtp.kernel.org \
    --to=mhiramat@kernel.org \
    --cc=kylebot@openai.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=outbounddisclosures@openai.com \
    --cc=rostedt@goodmis.org \
    --cc=stable@vger.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

all inboxes | Powered by JetHome®