linux-kernel - Re: SIGNAL_UNKILLABLE and init again

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 linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Mon, 14 Aug 2017 18:24:13 +0200
From:   Oleg Nesterov <oleg@...hat.com>
To:     Jamie Iles <jamie.iles@...cle.com>
Cc:     linux-kernel@...r.kernel.org
Subject: Re: SIGNAL_UNKILLABLE and init again

Hi Jamie,

On 08/14, Jamie Iles wrote:
>
> > > Not sure, let me think a bit more... and this is not enough anyway.
> > > 
> > > perhaps we should start with this simple change, but the "real" fix
> > > needs a lot of cleanups, although I am not sure if we will ever do this.
> > 
> > Okay, sounds good.  I'm happy to spend more time looking at this if you 
> > have suggestions - in the context of namespaces and containers this 
> > seems more relevant than when it was just the system init that we were 
> > protecting.
> 
> Any objections to moving ahead with this patch?

Oh, sorry.

OK, lets do this simple change then try to improve this logic further.

I'm afraid you need to re-send your patch, sorry.

Oleg.