[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250114143313.GA29305@redhat.com>
Date: Tue, 14 Jan 2025 15:33:13 +0100
From: Oleg Nesterov <oleg@...hat.com>
To: Eyal Birger <eyal.birger@...il.com>
Cc: Jiri Olsa <olsajiri@...il.com>, Aleksa Sarai <cyphar@...har.com>,
mhiramat@...nel.org, linux-kernel <linux-kernel@...r.kernel.org>,
linux-trace-kernel@...r.kernel.org,
BPF-dev-list <bpf@...r.kernel.org>,
Song Liu <songliubraving@...com>, Yonghong Song <yhs@...com>,
John Fastabend <john.fastabend@...il.com>, peterz@...radead.org,
tglx@...utronix.de, bp@...en8.de, x86@...nel.org,
linux-api@...r.kernel.org, Andrii Nakryiko <andrii@...nel.org>,
Daniel Borkmann <daniel@...earbox.net>,
Alexei Starovoitov <ast@...nel.org>,
Andrii Nakryiko <andrii.nakryiko@...il.com>,
"rostedt@...dmis.org" <rostedt@...dmis.org>, rafi@....io,
Shmulik Ladkani <shmulik.ladkani@...il.com>
Subject: Re: Crash when attaching uretprobes to processes running in Docker
On 01/14, Eyal Birger wrote:
>
> FWIW If I change the seccomp policy to SCMP_ACT_KILL this still fails.
Ah... I don't know what SCMP_ACT_KILL is, but indeed, in general it is
not safe to even try to call sys_uretprobe() if it is filtered.
Say, __secure_computing(SECCOMP_MODE_STRICT)->__secure_computing_strict()
does do_exit(SIGKILL) :/
Oleg.
Powered by blists - more mailing lists