[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <202504211604.EE9BD62F@keescook>
Date: Mon, 21 Apr 2025 16:04:56 -0700
From: Kees Cook <kees@...nel.org>
To: Jiri Olsa <jolsa@...nel.org>
Cc: Oleg Nesterov <oleg@...hat.com>, Peter Zijlstra <peterz@...radead.org>,
Andrii Nakryiko <andrii@...nel.org>,
Eyal Birger <eyal.birger@...il.com>, bpf@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-trace-kernel@...r.kernel.org,
x86@...nel.org, Song Liu <songliubraving@...com>,
Yonghong Song <yhs@...com>,
John Fastabend <john.fastabend@...il.com>,
Hao Luo <haoluo@...gle.com>, Steven Rostedt <rostedt@...dmis.org>,
Masami Hiramatsu <mhiramat@...nel.org>,
Alan Maguire <alan.maguire@...cle.com>,
David Laight <David.Laight@...lab.com>,
Thomas Weißschuh <thomas@...ch.de>,
Ingo Molnar <mingo@...nel.org>
Subject: Re: [PATCH perf/core 20/22] seccomp: passthrough uprobe systemcall
without filtering
On Mon, Apr 21, 2025 at 11:44:20PM +0200, Jiri Olsa wrote:
> Adding uprobe as another exception to the seccomp filter alongside
> with the uretprobe syscall.
>
> Same as the uretprobe the uprobe syscall is installed by kernel as
> replacement for the breakpoint exception and is limited to x86_64
> arch and isn't expected to ever be supported in i386.
>
> Cc: Kees Cook <keescook@...omium.org>
> Cc: Eyal Birger <eyal.birger@...il.com>
> Signed-off-by: Jiri Olsa <jolsa@...nel.org>
<insert standard grumbling>
Going forward, how can we avoid this kind of thing?
Reviewed-by: Kees Cook <kees@...nel.org>
--
Kees Cook
Powered by blists - more mailing lists