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
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Fri, 19 Nov 2021 09:03:56 -0600
From: (Eric W. Biederman)
To:     Kyle Huey <>
Cc:     open list <>,
        Linus Torvalds <>,
        Andrea Righi <>,
        Shuah Khan <>,
        Alexei Starovoitov <>,
        Andy Lutomirski <>,
        Will Drewry <>,
        "open list\:KERNEL SELFTEST FRAMEWORK" 
        <>, bpf <>,,
        "Robert O'Callahan" <>,
        Kees Cook <>,
        Oliver Sang <>,,
        kbuild test robot <>
Subject: Re: [PATCH 1/2] signal: Don't always set SA_IMMUTABLE for forced signals

Kyle Huey <> writes:

> On Thu, Nov 18, 2021 at 2:05 PM Eric W. Biederman <> 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/


>> Reported-by: Kyle Huey <>
>> Reported-by: kernel test robot <>
>> Cc:
>> [1]
>> [2]
> 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.


Powered by blists - more mailing lists