Oleg Nesterov writes:
> Eric, at al,
>
> Sorry, I am on on vacation, can't even read this thread right now,
> so I am not sure I understand the problem correctly...
That is fair. Please don't let me mess up your vacation.
The problem is an infinite stream of SIGHUP from a timer, making
process
Dmitry Vyukov writes:
> On Tue, Feb 5, 2019 at 4:26 PM Eric W. Biederman
> wrote:
>>
>>
>> Recently syzkaller was able to create unkillablle processes by
>> creating a timer that is delivered as a thread local signal on SIGHUP,
>> and receiving SIGHUP SA_NODEFERER. Ultimately causing a loop
>>
Eric, at al,
Sorry, I am on on vacation, can't even read this thread right now,
so I am not sure I understand the problem correctly...
On 02/05, Eric W. Biederman wrote:
>
> @@ -2393,6 +2393,11 @@ bool get_signal(struct ksignal *ksig)
> goto relock;
> }
>
> + /* Has this t
On Tue, Feb 5, 2019 at 4:26 PM Eric W. Biederman wrote:
>
>
> Recently syzkaller was able to create unkillablle processes by
> creating a timer that is delivered as a thread local signal on SIGHUP,
> and receiving SIGHUP SA_NODEFERER. Ultimately causing a loop
> failing to deliver SIGHUP but alwa
4 matches
Mail list logo
