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

Message-ID: <CAPM=9txT4k-BZv8nSaKSMNu=9EaOQi42uJERyb6vjsv-Q1j6FA@mail.gmail.com>
Date:	Tue, 26 May 2015 07:36:30 +1000
From:	Dave Airlie <airlied@...il.com>
To:	Oleg Nesterov <oleg@...hat.com>
Cc:	Richard Weinberger <richard@....at>,
	Dave Airlie <airlied@...ux.ie>,
	dri-devel <dri-devel@...ts.freedesktop.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: block_all_signals() usage in DRM

On 26 May 2015 at 02:50, Oleg Nesterov <oleg@...hat.com> wrote:
> 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.
>
> Dave. Lets finally kill this horror? I am going to send a patch unless
> you stop me ;)

There were follow up on that thread 4 years ago, but we are probably
at the stage where this thing can die,

I suspect any hw using it has died out, and any new hardware  won't be
doing evil things with drm locks

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/