[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Z6YJcPS3ujIx6AJP@krava>
Date: Fri, 7 Feb 2025 14:24:00 +0100
From: Jiri Olsa <olsajiri@...il.com>
To: Eyal Birger <eyal.birger@...il.com>
Cc: Kees Cook <kees@...nel.org>, luto@...capital.net, wad@...omium.org,
oleg@...hat.com, mhiramat@...nel.org, andrii@...nel.org,
olsajiri@...il.com, cyphar@...har.com, songliubraving@...com,
yhs@...com, john.fastabend@...il.com, peterz@...radead.org,
tglx@...utronix.de, bp@...en8.de, daniel@...earbox.net,
ast@...nel.org, andrii.nakryiko@...il.com, rostedt@...dmis.org,
rafi@....io, shmulik.ladkani@...il.com, bpf@...r.kernel.org,
linux-api@...r.kernel.org, linux-trace-kernel@...r.kernel.org,
x86@...nel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 0/2] seccomp: pass uretprobe system call through
seccomp
On Thu, Feb 06, 2025 at 05:06:29PM -0800, Eyal Birger wrote:
> On Thu, Feb 6, 2025 at 1:22 PM Kees Cook <kees@...nel.org> wrote:
> >
> > On Sun, 02 Feb 2025 08:29:19 -0800, Eyal Birger wrote:
> > > uretprobe(2) is an performance enhancement system call added to improve
> > > uretprobes on x86_64.
> > >
> > > Confinement environments such as Docker are not aware of this new system
> > > call and kill confined processes when uretprobes are attached to them.
> > >
> > > Since uretprobe is a "kernel implementation detail" system call which is
> > > not used by userspace application code directly, pass this system call
> > > through seccomp without forcing existing userspace confinement environments
> > > to be changed.
> > >
> > > [...]
> >
> > With the changes I mentioned in each patch, I've applied this to
> > for-next/seccomp, with the intention of getting them into v6.14-rc2.
> >
> > Thanks!
>
> Thank you very much for your help.
great!
thanks,
jirka
Powered by blists - more mailing lists