linux-kernel - Re: mm: use mmap_assert_write_locked() instead of open coding it

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: <20220331193257.c6e52c65346cbc21ba5a7bf5@linux-foundation.org>
Date:   Thu, 31 Mar 2022 19:32:57 -0700
From:   Andrew Morton <akpm@...ux-foundation.org>
To:     Rolf Eike Beer <eb@...ix.com>
Cc:     Christoph Hellwig <hch@...radead.org>, linux-mm@...ck.org,
        linux-kernel@...r.kernel.org
Subject: Re: mm: use mmap_assert_write_locked() instead of open coding it

On Tue, 29 Mar 2022 08:45:37 +0200 Rolf Eike Beer <eb@...ix.com> wrote:

> You are right, it was in tools/include/linux/kernel.h and I didn't spot the 
> prefix. Andrew, maybe you could just delete the sentence when you add the 
> Reviewed-by?

Did that.  I used simply "In case the lock is actually not held at this
point."