From: "Vlastimil Babka (SUSE)" <vbabka@kernel.org>
To: Suren Baghdasaryan <surenb@google.com>,
"Lorenzo Stoakes (ARM)" <ljs@kernel.org>
Cc: akpm@linux-foundation.org, dave.hansen@linux.intel.com,
Liam.Howlett@oracle.com, david@redhat.com, willy@infradead.org,
shakeel.butt@linux.dev, jannh@google.com, aliceryhl@google.com,
arve@android.com, cmllamas@google.com, christian@brauner.io,
tkjos@android.com, dsahern@kernel.org, davem@davemloft.net,
gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, netdev@vger.kernel.org
Subject: Re: [PATCH v3 3/5] mm: Add RCU-based VMA lookup helper that waits for writers
Date: Tue, 4 Aug 2026 09:59:26 +0200 [thread overview]
Message-ID: <6af71dfd-37b0-4489-8b7a-63478c8fdd4c@kernel.org> (raw)
In-Reply-To: <CAJuCfpEYFs94heKZn3hikYuCJU3CEHr2u1SSxXMyFQwHHAcjDg@mail.gmail.com>
On 8/3/26 21:13, Suren Baghdasaryan wrote:
> On Mon, Aug 3, 2026 at 9:44 AM Lorenzo Stoakes (ARM) <ljs@kernel.org> wrote:
>> Agree this is worth spelling out in the comment (I raised similarly).
>>
>> Maybe something like:
>>
>> If a VMA exists which spans @address, return that VMA, read-locked.
>>
>> If no VMA is mapped there or, very unlikely, a reference count overflow
>> occurred, return NULL.
>>
>> Nothing prevents VMAs being unmapped/mapped before or after the VMA is
>> looked up, if a stronger guarantee is required, take an mmap lock.
>
> This last statement is true only if the function returns NULL, so I
> think it should be in the same paragraph as the "If no VMA is
> mapped..." sentence and prepended with "In this case...". So:
>
> If no VMA is mapped there or, very unlikely, a reference count overflow
> occurred, return NULL. In this case, nothing prevents VMAs
> being unmapped/
> mapped before or after the VMA is looked up, if a stronger guarantee is
> required, take an mmap lock.
>
> Does that sounds good?
Yeah, thanks both!
next prev parent reply other threads:[~2026-08-04 7:59 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-02 21:54 [PATCH v3 0/5] mm: Unconditional per-VMA locks and cleanups Suren Baghdasaryan
2026-08-02 21:54 ` [PATCH v3 1/5] mm: Make per-VMA locks available universally Suren Baghdasaryan
2026-08-03 10:49 ` Lorenzo Stoakes (ARM)
2026-08-03 14:01 ` Vlastimil Babka (SUSE)
2026-08-03 17:45 ` Suren Baghdasaryan
2026-08-03 15:24 ` Suren Baghdasaryan
2026-08-03 16:08 ` Lorenzo Stoakes (ARM)
2026-08-03 17:41 ` Suren Baghdasaryan
2026-08-03 17:45 ` Suren Baghdasaryan
2026-08-03 21:12 ` Jann Horn
2026-08-04 8:56 ` Lorenzo Stoakes (ARM)
2026-08-04 14:59 ` Suren Baghdasaryan
2026-08-03 19:33 ` Jann Horn
2026-08-03 19:43 ` Suren Baghdasaryan
2026-08-02 21:54 ` [PATCH v3 2/5] binder: Make shrinker rely solely on per-VMA lock Suren Baghdasaryan
2026-08-03 9:48 ` Alice Ryhl
2026-08-03 10:50 ` Lorenzo Stoakes (ARM)
2026-08-03 11:11 ` Lorenzo Stoakes (ARM)
2026-08-03 11:33 ` Lorenzo Stoakes (ARM)
2026-08-03 18:02 ` Suren Baghdasaryan
2026-08-04 9:15 ` Lorenzo Stoakes (ARM)
2026-08-03 11:10 ` Lorenzo Stoakes (ARM)
2026-08-03 18:31 ` Suren Baghdasaryan
2026-08-04 9:08 ` Lorenzo Stoakes (ARM)
2026-08-04 9:04 ` Alice Ryhl
2026-08-04 9:11 ` Lorenzo Stoakes (ARM)
2026-08-04 14:54 ` Suren Baghdasaryan
2026-08-02 21:54 ` [PATCH v3 3/5] mm: Add RCU-based VMA lookup helper that waits for writers Suren Baghdasaryan
2026-08-03 11:28 ` Lorenzo Stoakes (ARM)
2026-08-03 19:01 ` Suren Baghdasaryan
2026-08-04 8:47 ` Lorenzo Stoakes (ARM)
2026-08-04 15:00 ` Suren Baghdasaryan
2026-08-03 14:55 ` Vlastimil Babka (SUSE)
2026-08-03 15:00 ` Lorenzo Stoakes (ARM)
2026-08-03 16:24 ` Vlastimil Babka (SUSE)
2026-08-03 16:43 ` Lorenzo Stoakes (ARM)
2026-08-03 19:13 ` Suren Baghdasaryan
2026-08-04 7:59 ` Vlastimil Babka (SUSE) [this message]
2026-08-04 8:44 ` Lorenzo Stoakes (ARM)
2026-08-02 21:54 ` [PATCH v3 4/5] binder: Remove mmap_lock fallback Suren Baghdasaryan
2026-08-03 10:34 ` Alice Ryhl
2026-08-03 19:14 ` Suren Baghdasaryan
2026-08-03 11:33 ` Lorenzo Stoakes (ARM)
2026-08-03 19:16 ` Suren Baghdasaryan
2026-08-02 21:54 ` [PATCH v3 5/5] tcp: Remove mmap_lock fallback path Suren Baghdasaryan
2026-08-03 2:11 ` [PATCH v3 0/5] mm: Unconditional per-VMA locks and cleanups Barry Song
2026-08-03 17:51 ` Suren Baghdasaryan
2026-08-04 9:27 ` Lorenzo Stoakes (ARM)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6af71dfd-37b0-4489-8b7a-63478c8fdd4c@kernel.org \
--to=vbabka@kernel.org \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=aliceryhl@google.com \
--cc=arve@android.com \
--cc=christian@brauner.io \
--cc=cmllamas@google.com \
--cc=dave.hansen@linux.intel.com \
--cc=davem@davemloft.net \
--cc=david@redhat.com \
--cc=dsahern@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=jannh@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=shakeel.butt@linux.dev \
--cc=surenb@google.com \
--cc=tkjos@android.com \
--cc=willy@infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox