linux-kernel - Re: block_all_signals() usage in DRM

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <55635896.1040600@nod.at>
Date:	Mon, 25 May 2015 19:15:02 +0200
From:	Richard Weinberger <richard@....at>
To:	Oleg Nesterov <oleg@...hat.com>
CC:	airlied@...ux.ie, dri-devel@...ts.freedesktop.org,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: block_all_signals() usage in DRM

Am 25.05.2015 um 18:50 schrieb Oleg Nesterov:
> AAAAOn 05/25, Richard Weinberger wrote:
>>
>> Is this functionality still in use/needed?
> 
> All I can say it doesn't work.
> 
>> Otherwise we could get rid of block_all_signals() and unpuzzle the signaling
>> code a bit. :-)
> 
> Yes. I do not even remember when I reported this the first time. Perhaps
> more than 10 years ago.
> 
> See the last attempt in 2011: https://lkml.org/lkml/2011/7/12/263
> I copied this email below.

Thank you Oleg, this makes sense.
I was actually wondering WTF this function is good for.

Thanks,
//richard
--
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/