[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAP045Aq06LV_jbXVc85bYU62h5EoVQ=rD9pDn+nGaUJ+iWe62w@mail.gmail.com>
Date: Fri, 19 Nov 2021 08:07:36 -0800
From: Kyle Huey <me@...ehuey.com>
To: "Eric W. Biederman" <ebiederm@...ssion.com>
Cc: Kees Cook <keescook@...omium.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>,
open list <linux-kernel@...r.kernel.org>,
linux-hardening@...r.kernel.org,
"Robert O'Callahan" <rocallahan@...il.com>
Subject: Re: [REGRESSION] 5.16rc1: SA_IMMUTABLE breaks debuggers
On Thu, Nov 18, 2021 at 8:12 AM Eric W. Biederman <ebiederm@...ssion.com> wrote:
> Kyle thank you for your explanation of what breaks. For future kernels
> I do need to do some work in this area and I will copy on the patches
> going forward. In particular I strongly suspect that changing the
> sigaction and blocked state of the signal for these synchronous signals
> is the wrong thing to do, especially if the process is not killed. I
> want to find another solution that does not break things but that also
> does not change the program state behind the programs back so things
> work differently under the debugger.
The heads up in the future is appreciated, thanks.
- Kyle
Powered by blists - more mailing lists