From: "Lorenzo Stoakes (ARM)" <ljs@kernel.org>
To: Suren Baghdasaryan <surenb@google.com>
Cc: akpm@linux-foundation.org, dave.hansen@linux.intel.com,
Liam.Howlett@oracle.com, david@kernel.org, willy@infradead.org,
shakeel.butt@linux.dev, vbabka@kernel.org, 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 v4 2/5] binder: Make shrinker rely solely on per-VMA lock
Date: Mon, 10 Aug 2026 11:22:03 +0100 [thread overview]
Message-ID: <anmlTpwKW-c51wYB@lucifer> (raw)
In-Reply-To: <20260806200548.3124802-3-surenb@google.com>
On Thu, Aug 06, 2026 at 01:05:45PM -0700, Suren Baghdasaryan wrote:
> From: Dave Hansen <dave.hansen@linux.intel.com>
>
> tl;dr: lock_vma_under_rcu() is already a trylock. No need to do both
> it and mmap_read_trylock().
>
> Long Version:
>
> == Background ==
>
> Historically, binder used an mmap_read_trylock() in its shrinker code.
> This ensures that reclaim is not blocked on an mmap_lock. Commit
> 95bc2d4a9020 ("binder: use per-vma lock in page reclaiming") added
> support for the per-VMA lock, but left mmap_read_trylock() as a
> fallback.
>
> This was presumably because the per-VMA locking can fail for several
> reasons and most (all?) lock_vma_under_rcu() callers have a fallback
> to mmap_read_trylock().
>
> == Problem ==
>
> The fallback is not worth the complexity here. lock_vma_under_rcu() is
> essentially already a non-blocking trylock. The main reason it fails
> is also the reason mmap_read_trylock() fails: something is holding
> mmap_write_lock().
>
> The only remedy for a collision with mmap_write_lock() is to wait,
> which this code can not do. So the "fallback" after
> lock_vma_under_rcu() failure is not really a fallback: it is really
> likely to just be retrying in vain. That retry in an of itself isn't
> horrible. But it adds complexity.
>
> == Solution ==
>
> Now that per-VMA locks are universally available, lock_vma_under_rcu()
> will not persistently fail. Rely on it alone and simplify the code.
> The removal of the fallback does not affect NOMMU case because binder
> driver depends on CONFIG_MMU.
>
> Full disclosure: I originally tried to do this with
> lock_vma_under_rcu_wait(), but it did not fit well with the mmap_lock
> trylock semantics. Claude caught this in a review and suggested the
> approach in this path. It seemed sane to me. So, Suggesed-by: Claude,
> I guess.
>
> Signed-off-by: Dave Hansen <dave.hansen@linux.intel.com>
> Signed-off-by: Suren Baghdasaryan <surenb@google.com>
Thanks, LGTM so:
Acked-by: Lorenzo Stoakes (ARM) <ljs@kernel.org>
> Cc: Andrew Morton <akpm@linux-foundation.org>
> Cc: "Liam R. Howlett" <Liam.Howlett@oracle.com>
> Cc: Vlastimil Babka <vbabka@kernel.org>
> Cc: Shakeel Butt <shakeel.butt@linux.dev>
> Cc: linux-mm@kvack.org
> Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> Cc: Arve Hjønnevåg <arve@android.com>
> Cc: Todd Kjos <tkjos@android.com>
> Cc: Christian Brauner <christian@brauner.io>
> Cc: Carlos Llamas <cmllamas@google.com>
> Cc: Alice Ryhl <aliceryhl@google.com>
> Cc: "David S. Miller" <davem@davemloft.net>
> Cc: David Ahern <dsahern@kernel.org>
> Cc: netdev@vger.kernel.org
> ---
> drivers/android/binder_alloc.c | 45 ++++++++++++++++------------------
> 1 file changed, 21 insertions(+), 24 deletions(-)
>
> diff --git a/drivers/android/binder_alloc.c b/drivers/android/binder_alloc.c
> index e4488ad86a65..c13a588c37de 100644
> --- a/drivers/android/binder_alloc.c
> +++ b/drivers/android/binder_alloc.c
> @@ -1142,7 +1142,6 @@ enum lru_status binder_alloc_free_page(struct list_head *item,
> struct vm_area_struct *vma;
> struct page *page_to_free;
> unsigned long page_addr;
> - int mm_locked = 0;
> size_t index;
>
> if (!mmget_not_zero(mm))
> @@ -1151,27 +1150,25 @@ enum lru_status binder_alloc_free_page(struct list_head *item,
> index = mdata->page_index;
> page_addr = alloc->vm_start + index * PAGE_SIZE;
>
> - /* attempt per-vma lock first */
> + /*
> + * Attempt per-vma lock. This is essentially a
> + * "trylock". It can fail even if the VMA exists
> + * for 'page_addr'.
> + */
> vma = lock_vma_under_rcu(mm, page_addr);
> if (!vma) {
> - /* fall back to mmap_lock */
> - if (!mmap_read_trylock(mm))
> - goto err_mmap_read_lock_failed;
> - mm_locked = 1;
> - vma = vma_lookup(mm, page_addr);
> + /*
> + * If the vma exists, we can't continue because we cannot
> + * remove the page from the vma. However, if the vma was
> + * unmapped, it's okay to continue.
> + */
> + if (binder_alloc_is_mapped(alloc))
> + goto err_vma_lock_failed;
> }
>
> if (!mutex_trylock(&alloc->mutex))
> goto err_get_alloc_mutex_failed;
>
> - /*
> - * Since a binder_alloc can only be mapped once, we ensure
> - * the vma corresponds to this mapping by checking whether
> - * the binder_alloc is still mapped.
> - */
> - if (vma && !binder_alloc_is_mapped(alloc))
> - goto err_invalid_vma;
> -
> trace_binder_unmap_kernel_start(alloc, index);
>
> page_to_free = alloc->pages[index];
> @@ -1182,7 +1179,12 @@ enum lru_status binder_alloc_free_page(struct list_head *item,
> list_lru_isolate(lru, item);
> spin_unlock(&lru->lock);
>
> - if (vma) {
> + /*
> + * Since a binder_alloc can only be mapped once, we ensure
> + * the vma corresponds to this mapping by checking whether
> + * the binder_alloc is still mapped.
> + */
> + if (vma && binder_alloc_is_mapped(alloc)) {
> trace_binder_unmap_user_start(alloc, index);
>
> zap_vma_range(vma, page_addr, PAGE_SIZE);
> @@ -1191,23 +1193,18 @@ enum lru_status binder_alloc_free_page(struct list_head *item,
> }
>
> mutex_unlock(&alloc->mutex);
> - if (mm_locked)
> - mmap_read_unlock(mm);
> - else
> + if (vma)
> vma_end_read(vma);
> mmput_async(mm);
> binder_free_page(page_to_free);
>
> return LRU_REMOVED_RETRY;
>
> -err_invalid_vma:
> mutex_unlock(&alloc->mutex);
> err_get_alloc_mutex_failed:
> - if (mm_locked)
> - mmap_read_unlock(mm);
> - else
> + if (vma)
> vma_end_read(vma);
> -err_mmap_read_lock_failed:
> +err_vma_lock_failed:
> mmput_async(mm);
> err_mmget:
> return LRU_SKIP;
> --
> 2.55.0.654.g21b8a5bc05-goog
>
--
Cheers, Lorenzo
next prev parent reply other threads:[~2026-08-10 10:22 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-06 20:05 [PATCH v4 0/5] mm: Unconditional per-VMA locks and cleanups Suren Baghdasaryan
2026-08-06 20:05 ` [PATCH v4 1/5] mm: Make per-VMA locks available universally Suren Baghdasaryan
2026-08-07 15:37 ` Vlastimil Babka (SUSE)
2026-08-08 1:12 ` Matthew Wilcox
2026-08-08 6:08 ` Suren Baghdasaryan
2026-08-10 8:52 ` Lorenzo Stoakes (ARM)
2026-08-10 9:42 ` Lorenzo Stoakes (ARM)
2026-08-10 16:40 ` Suren Baghdasaryan
2026-08-10 10:17 ` Lorenzo Stoakes (ARM)
2026-08-10 15:22 ` Dave Hansen
2026-08-10 15:56 ` Matthew Wilcox
2026-08-10 17:04 ` Suren Baghdasaryan
2026-08-06 20:05 ` [PATCH v4 2/5] binder: Make shrinker rely solely on per-VMA lock Suren Baghdasaryan
2026-08-07 14:26 ` Alice Ryhl
2026-08-10 10:22 ` Lorenzo Stoakes (ARM) [this message]
2026-08-10 18:32 ` Carlos Llamas
2026-08-10 18:54 ` Suren Baghdasaryan
2026-08-10 19:16 ` Carlos Llamas
2026-08-10 18:57 ` Carlos Llamas
2026-08-06 20:05 ` [PATCH v4 3/5] mm: Add RCU-based VMA lookup helper that waits for writers Suren Baghdasaryan
2026-08-07 15:39 ` Vlastimil Babka (SUSE)
2026-08-08 7:24 ` Matthew Wilcox
2026-08-09 1:07 ` Suren Baghdasaryan
2026-08-10 10:24 ` Lorenzo Stoakes (ARM)
2026-08-10 15:25 ` Dave Hansen
2026-08-08 7:37 ` Matthew Wilcox
2026-08-10 10:41 ` Lorenzo Stoakes (ARM)
2026-08-10 17:07 ` Suren Baghdasaryan
2026-08-06 20:05 ` [PATCH v4 4/5] binder: Remove mmap_lock fallback Suren Baghdasaryan
2026-08-06 20:05 ` [PATCH v4 5/5] tcp: Remove mmap_lock fallback path Suren Baghdasaryan
2026-08-08 7:26 ` Matthew Wilcox
2026-08-09 0:51 ` Suren Baghdasaryan
2026-08-10 15:26 ` Dave Hansen
2026-08-10 17:09 ` Suren Baghdasaryan
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=anmlTpwKW-c51wYB@lucifer \
--to=ljs@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@kernel.org \
--cc=dsahern@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=jannh@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=netdev@vger.kernel.org \
--cc=shakeel.butt@linux.dev \
--cc=surenb@google.com \
--cc=tkjos@android.com \
--cc=vbabka@kernel.org \
--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