linux-kernel - Re: [PATCH 1/1] signals: kill block_all_signals() and unblock_all

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]

Message-ID: <CAPM=9tw3X=khc0dJq3qwx22A+iMk1cO0dOLJHkXJipd3s=+YPA@mail.gmail.com>
Date:	Wed, 16 Sep 2015 09:53:33 +1000
From:	Dave Airlie <airlied@...il.com>
To:	Oleg Nesterov <oleg@...hat.com>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	Richard Weinberger <richard@....at>,
	dri-devel <dri-devel@...ts.freedesktop.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 1/1] signals: kill block_all_signals() and unblock_all_signals()

On 16 September 2015 at 02:41, Oleg Nesterov <oleg@...hat.com> wrote:
> ping ;)
>
> Andrew, should I re-send this patch? It was acked by Daniel and Dave
> doesn't object.
>
> Dave, I'll appreciate it if you ack it explicitly.
>
>
> On 08/27, Oleg Nesterov wrote:
>>
>> It is hardly possible to enumerate all problems with block_all_signals()
>> and unblock_all_signals(). Just for example,
>>
>> 1. block_all_signals(SIGSTOP/etc) simply can't help if the caller is
>>    multithreaded. Another thread can dequeue the signal and force the
>>    group stop.
>>
>> 2. Even is the caller is single-threaded, it will "stop" anyway. It
>>    will not sleep, but it will spin in kernel space until SIGCONT or
>>    SIGKILL.
>>
>> And a lot more. In short, this interface doesn't work at all, at least
>> the last 10+ years.
>>
>> Signed-off-by: Oleg Nesterov <oleg@...hat.com>

Acked-by: Dave Airlie <airlied@...hat.com>

Probably best to go via Andrew alright.

Dave.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/