lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Fri, 19 Nov 2021 09:03:56 -0600 From: ebiederm@...ssion.com (Eric W. Biederman) To: Kyle Huey <me@...ehuey.com> Cc: open list <linux-kernel@...r.kernel.org>, Linus Torvalds <torvalds@...ux-foundation.org>, Andrea Righi <andrea.righi@...onical.com>, Shuah Khan <shuah@...nel.org>, Alexei Starovoitov <ast@...nel.org>, Andy Lutomirski <luto@...capital.net>, Will Drewry <wad@...omium.org>, "open list\:KERNEL SELFTEST FRAMEWORK" <linux-kselftest@...r.kernel.org>, bpf <bpf@...r.kernel.org>, linux-hardening@...r.kernel.org, "Robert O'Callahan" <rocallahan@...il.com>, Kees Cook <keescook@...omium.org>, Oliver Sang <oliver.sang@...el.com>, lkp@...ts.01.org, kbuild test robot <lkp@...el.com> Subject: Re: [PATCH 1/2] signal: Don't always set SA_IMMUTABLE for forced signals Kyle Huey <me@...ehuey.com> writes: > On Thu, Nov 18, 2021 at 2:05 PM Eric W. Biederman <ebiederm@...ssion.com> wrote: >> >> >> Recently to prevent issues with SECCOMP_RET_KILL and similar signals >> being changed before they are delivered SA_IMMUTABLE was added. >> >> Unfortunately this broke debuggers[1][2] which reasonably expect to be >> able to trap synchronous SIGTRAP and SIGSEGV even when the target >> process is not configured to handle those signals. >> >> Update force_sig_to_task to support both the case when we can >> allow the debugger to intercept and possibly ignore the >> signal and the case when it is not safe to let userspace >> known about the signal until the process has exited. > > s/known/know/ Fixed. >> Reported-by: Kyle Huey <me@...ehuey.com> >> Reported-by: kernel test robot <oliver.sang@...el.com> >> Cc: stable@...r.kernel.org >> [1] https://lkml.kernel.org/r/CAP045AoMY4xf8aC_4QU_-j7obuEPYgTcnQQP3Yxk=2X90jtpjw@mail.gmail.com >> [2] https://lkml.kernel.org/r/20211117150258.GB5403@xsang-OptiPlex-902 > > This link doesn't work. Shame. I missed a trailing 0, but unfortunately that request did not go to list that is archived on lore. I will keep the link on the chance the message winds up in a lore archive in the future. Eric
Powered by blists - more mailing lists