linux-kernel - Re: mm: use down_read_killable for locking mmap_sem in access_remote

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: <20190515083825.GJ13687@blackbody.suse.cz>
Date:   Wed, 15 May 2019 10:38:26 +0200
From:   Michal Koutný <mkoutny@...e.com>
To:     khlebnikov@...dex-team.ru
Cc:     akpm@...ux-foundation.org, linux-kernel@...r.kernel.org,
        linux-mm@...ck.org, oleg@...hat.com
Subject: Re: mm: use down_read_killable for locking mmap_sem in
 access_remote_vm

Hi,
making this holder of mmap_sem killable was for the reasons of /proc/...
diagnostics was an idea I was pondeering too. However, I think the
approach of pretending we read 0 bytes is not correct. The API would IMO
need to be extended to allow pass a result such as EINTR to the end
caller.
Why do you think it's safe to return just 0?

Michal

Download attachment "signature.asc" of type "application/pgp-signature" (834 bytes)