linux-kernel - Re: [RFC PATCH] docs/mm: add VMA locks documentation

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: <645ad352-5eff-4ad1-997c-ad249b2cd9a1@lucifer.local>
Date: Tue, 5 Nov 2024 16:11:40 +0000
From: Lorenzo Stoakes <lorenzo.stoakes@...cle.com>
To: Suren Baghdasaryan <surenb@...gle.com>
Cc: Jonathan Corbet <corbet@....net>,
        Andrew Morton <akpm@...ux-foundation.org>,
        "Liam R . Howlett" <Liam.Howlett@...cle.com>,
        Vlastimil Babka <vbabka@...e.cz>, Jann Horn <jannh@...gle.com>,
        Alice Ryhl <aliceryhl@...gle.com>, Boqun Feng <boqun.feng@...il.com>,
        Matthew Wilcox <willy@...radead.org>, Mike Rapoport <rppt@...nel.org>,
        linux-mm@...ck.org, linux-kernel@...r.kernel.org
Subject: Re: [RFC PATCH] docs/mm: add VMA locks documentation

On Mon, Nov 04, 2024 at 01:20:14PM -0800, Suren Baghdasaryan wrote:
[snip]
> Sounds good! I think it would be good to separate design decisions (mm
> should be write-locked before any VMA can be write-locked, all
> write-locked VMAs and automatically unlocked once mm is
> write-unlocked, etc) vs implementation details (lock_vma_under_rcu(),
> vma->vm_lock_seq, mm->mm_lock_seq, etc). Easily said than done :)

Yeah, was saying the same to Jann - probably best to have an explicit separate
section for implementation details with the rest providing readable + pertinent
details for _users_ of these interfaces.