From: Jann Horn <jannh@google.com>
To: Alice Ryhl <aliceryhl@google.com>
Cc: "Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Carlos Llamas" <cmllamas@google.com>,
"Miguel Ojeda" <ojeda@kernel.org>,
"Boqun Feng" <boqun@kernel.org>, "Gary Guo" <gary@garyguo.net>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Benno Lossin" <lossin@kernel.org>,
"Andreas Hindborg" <a.hindborg@kernel.org>,
"Trevor Gross" <tmgross@umich.edu>,
"Danilo Krummrich" <dakr@kernel.org>,
"Lorenzo Stoakes" <lorenzo.stoakes@oracle.com>,
"Liam R. Howlett" <Liam.Howlett@oracle.com>,
linux-kernel@vger.kernel.org, rust-for-linux@vger.kernel.org,
linux-mm@kvack.org
Subject: Re: [PATCH] rust_binder: use lock_vma_under_rcu() in use_page_slow()
Date: Wed, 18 Feb 2026 17:21:01 +0100 [thread overview]
Message-ID: <CAG48ez2v3RoHhOiKYJqBA=UvF+0PnKCZMLiemztTFxNwc4gH=A@mail.gmail.com> (raw)
In-Reply-To: <20260218-binder-vma-rcu-v1-1-8bd45b2b1183@google.com>
On Wed, Feb 18, 2026 at 4:13 PM Alice Ryhl <aliceryhl@google.com> wrote:
> There's no reason to lock the whole mm when we are doing operations on
> the vma if we can help it, so to reduce contention, use the
> lock_vma_under_rcu() abstraction.
>
> Signed-off-by: Alice Ryhl <aliceryhl@google.com>
Reviewed-by: Jann Horn <jannh@google.com>
> ---
> Depends on:
> https://lore.kernel.org/all/20260218-binder-vma-check-v2-0-60f9d695a990@google.com/
> ---
> drivers/android/binder/page_range.rs | 37 ++++++++++++++++++------------------
> 1 file changed, 19 insertions(+), 18 deletions(-)
>
> diff --git a/drivers/android/binder/page_range.rs b/drivers/android/binder/page_range.rs
> index 67aae783e8b8b7cf60ecf7e711d5f6f6f5d1dbe3..9dfc154e5dd4e889c4f3aa89e5edb89434113e1a 100644
> --- a/drivers/android/binder/page_range.rs
> +++ b/drivers/android/binder/page_range.rs
> @@ -435,24 +435,25 @@ unsafe fn use_page_slow(&self, i: usize) -> Result<()> {
> //
> // Using `mmput_async` avoids this, because then the `mm` cleanup is instead queued to a
> // workqueue.
> - check_vma(
> - MmWithUser::into_mmput_async(self.mm.mmget_not_zero().ok_or(ESRCH)?)
> - .mmap_read_lock()
> - .vma_lookup(vma_addr)
> - .ok_or(ESRCH)?,
> - self,
> - )
> - .ok_or(ESRCH)?
> - .vm_insert_page(user_page_addr, &new_page)
> - .inspect_err(|err| {
> - pr_warn!(
> - "Failed to vm_insert_page({}): vma_addr:{} i:{} err:{:?}",
> - user_page_addr,
> - vma_addr,
> - i,
> - err
> - )
> - })?;
> + let mm = MmWithUser::into_mmput_async(self.mm.mmget_not_zero().ok_or(ESRCH)?);
> + {
> + let vma_read;
> + let mmap_read;
> + let vma = if let Some(ret) = mm.lock_vma_under_rcu(vma_addr) {
> + vma_read = ret;
> + check_vma(&vma_read, self)
nit: this might look nicer if the check_vma() calls were moved out of
the two separate branches
> + } else {
> + mmap_read = mm.mmap_read_lock();
> + mmap_read
> + .vma_lookup(vma_addr)
> + .and_then(|vma| check_vma(vma, self))
> + };
> +
> + match vma {
> + Some(vma) => vma.vm_insert_page(user_page_addr, &new_page)?,
> + None => return Err(ESRCH),
> + }
> + }
prev parent reply other threads:[~2026-02-18 16:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-18 15:13 Alice Ryhl
2026-02-18 16:16 ` Liam R. Howlett
2026-02-18 16:21 ` Jann Horn [this message]
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='CAG48ez2v3RoHhOiKYJqBA=UvF+0PnKCZMLiemztTFxNwc4gH=A@mail.gmail.com' \
--to=jannh@google.com \
--cc=Liam.Howlett@oracle.com \
--cc=a.hindborg@kernel.org \
--cc=aliceryhl@google.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun@kernel.org \
--cc=cmllamas@google.com \
--cc=dakr@kernel.org \
--cc=gary@garyguo.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=lossin@kernel.org \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=tmgross@umich.edu \
/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