linux-kernel - Re: [PATCH] signal: protect SIGNAL_UNKILLABLE from unintentional clearing.

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 for Android: free password hash cracker in your pocket

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

Message-ID: <20161117190420.GA23492@redhat.com>
Date:   Thu, 17 Nov 2016 20:04:20 +0100
From:   Oleg Nesterov <oleg@...hat.com>
To:     Jamie Iles <jamie.iles@...cle.com>
Cc:     linux-kernel@...r.kernel.org,
        Alexander Viro <viro@...iv.linux.org.uk>,
        Ingo Molnar <mingo@...hat.com>,
        Peter Zijlstra <peterz@...radead.org>,
        Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH] signal: protect SIGNAL_UNKILLABLE from unintentional
        clearing.

On 11/16, Jamie Iles wrote:
>
> This can result in init becoming stoppable/killable after tracing.  For
> example, running:
>
>   while true; do kill -STOP 1; done &
>   strace -p 1

> and then stopping strace and the kill loop will result in init being
> left in state TASK_STOPPED.  Sending SIGCONT to init will resume it, but
> init will now respond to future SIGSTOP signals rather than ignoring
> them.

Yes, and a lot more... I forgot about these problems again.

Jamie, sorry for delay, I'll try to read the patch and reply tomorrow.

Oleg.