linux-kernel - Re: [PATCH] /dev/[k]mem: make reads and writes interruptible

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]

Date:   Thu, 7 Apr 2022 10:14:40 +0200
From:   David Hildenbrand <david@...hat.com>
To:     "Jason A. Donenfeld" <Jason@...c4.com>,
        linux-kernel@...r.kernel.org, gregkh@...uxfoundation.org
Cc:     Tetsuo Handa <penguin-kernel@...ove.SAKURA.ne.jp>
Subject: Re: [PATCH] /dev/[k]mem: make reads and writes interruptible

On 07.04.22 02:13, Jason A. Donenfeld wrote:
> In 8619e5bdeee8 ("/dev/mem: Bail out upon SIGKILL."), /dev/[k]mem became
> killable, and that commit noted:
> 
>   Theoretically, reading/writing /dev/mem and /dev/kmem can become
>   "interruptible". But this patch chose "killable". Future patch will
>   make them "interruptible" so that we can revert to "killable" if
>   some program regressed.
> 
> So now we take the next step in making it "interruptible", by changing
> fatal_signal_pending() into signal_pending().

/dev/kmem is no more. So this should only apply to /dev/mem nowadays.


-- 
Thanks,

David / dhildenb