From: Hillf Danton <hdanton@sina.com>
To: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Suren Baghdasaryan <surenb@google.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Boqun Feng <boqun.feng@gmail.com>,
Waiman Long <longman@redhat.com>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Subject: Re: [PATCH RESEND v3 10/10] mm/vma: add and use vma_assert_stabilised()
Date: Sat, 24 Jan 2026 07:35:48 +0800 [thread overview]
Message-ID: <20260123233550.2378-1-hdanton@sina.com> (raw)
In-Reply-To: <43c90424ba0874a71bb7ab9d6423b3a2bf616f8e.1769086312.git.lorenzo.stoakes@oracle.com>
On Thu, 22 Jan 2026 13:02:02 +0000 Lorenzo Stoakes wrote:
> +/**
> + * vma_assert_stabilised() - assert that this VMA cannot be changed from
> + * underneath us either by having a VMA or mmap lock held.
> + * @vma: The VMA whose stability we wish to assess.
> + *
> + * If lockdep is enabled we can precisely ensure stability via either an mmap
> + * lock owned by us or a specific VMA lock.
> + *
> + * With lockdep disabled we may sometimes race with other threads acquiring the
> + * mmap read lock simultaneous with our VMA read lock.
> + */
> +static inline void vma_assert_stabilised(struct vm_area_struct *vma)
> +{
> + /*
> + * If another thread owns an mmap lock, it may go away at any time, and
> + * thus is no guarantee of stability.
> + *
> + * If lockdep is enabled we can accurately determine if an mmap lock is
> + * held and owned by us. Otherwise we must approximate.
> + *
> + * It doesn't necessarily mean we are not stabilised however, as we may
> + * hold a VMA read lock (not a write lock as this would require an owned
> + * mmap lock).
> + *
> + * If (assuming lockdep is not enabled) we were to assert a VMA read
> + * lock first we may also run into issues, as other threads can hold VMA
> + * read locks simlutaneous to us.
> + *
> + * Therefore if lockdep is not enabled we risk a false negative (i.e. no
> + * assert fired). If accurate checking is required, enable lockdep.
> + */
> + if (IS_ENABLED(CONFIG_LOCKDEP)) {
> + if (lockdep_is_held(&vma->vm_mm->mmap_lock))
> + return;
> + } else {
> + if (rwsem_is_locked(&vma->vm_mm->mmap_lock))
> + return;
> + }
In case of the mmap_lock, rwsem_is_locked has nothing to do with lockdep_is_held,
as the latter is noop without lockdep enabled. And the former fails to match the
us in "assert that this VMA cannot be changed from underneath us either by having
a VMA or mmap lock held".
That said, you are adding confusion.
> +
> + /*
> + * We're not stabilised by the mmap lock, so assert that we're
> + * stabilised by a VMA lock.
> + */
> + vma_assert_locked(vma);
> +}
> +
next prev parent reply other threads:[~2026-01-24 0:54 UTC|newest]
Thread overview: 73+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-22 13:01 [PATCH RESEND v3 00/10] mm: add and use vma_assert_stabilised() helper Lorenzo Stoakes
2026-01-22 13:01 ` [PATCH RESEND v3 01/10] mm/vma: rename VMA_LOCK_OFFSET to VM_REFCNT_EXCLUDE_READERS_FLAG Lorenzo Stoakes
2026-01-22 16:26 ` Vlastimil Babka
2026-01-22 16:29 ` Lorenzo Stoakes
2026-01-23 13:52 ` Lorenzo Stoakes
2026-01-22 16:37 ` Suren Baghdasaryan
2026-01-23 13:26 ` Lorenzo Stoakes
2026-01-22 13:01 ` [PATCH RESEND v3 02/10] mm/vma: document possible vma->vm_refcnt values and reference comment Lorenzo Stoakes
2026-01-22 16:48 ` Vlastimil Babka
2026-01-22 17:28 ` Suren Baghdasaryan
2026-01-23 15:06 ` Lorenzo Stoakes
2026-01-23 13:45 ` Lorenzo Stoakes
2026-01-22 13:01 ` [PATCH RESEND v3 03/10] mm/vma: rename is_vma_write_only(), separate out shared refcount put Lorenzo Stoakes
2026-01-22 17:36 ` Vlastimil Babka
2026-01-22 19:31 ` Suren Baghdasaryan
2026-01-23 8:24 ` Vlastimil Babka
2026-01-23 14:52 ` Lorenzo Stoakes
2026-01-23 15:05 ` Vlastimil Babka
2026-01-23 15:07 ` Lorenzo Stoakes
2026-01-23 14:41 ` Lorenzo Stoakes
2026-01-26 10:04 ` Lorenzo Stoakes
2026-01-23 14:02 ` Lorenzo Stoakes
2026-01-22 13:01 ` [PATCH RESEND v3 04/10] mm/vma: add+use vma lockdep acquire/release defines Lorenzo Stoakes
2026-01-22 19:32 ` Suren Baghdasaryan
2026-01-22 19:41 ` Suren Baghdasaryan
2026-01-23 8:41 ` Vlastimil Babka
2026-01-23 15:08 ` Lorenzo Stoakes
2026-01-23 15:00 ` Lorenzo Stoakes
2026-01-23 8:48 ` Vlastimil Babka
2026-01-23 15:10 ` Lorenzo Stoakes
2026-01-22 13:01 ` [PATCH RESEND v3 05/10] mm/vma: de-duplicate __vma_enter_locked() error path Lorenzo Stoakes
2026-01-22 19:39 ` Suren Baghdasaryan
2026-01-23 15:11 ` Lorenzo Stoakes
2026-01-23 8:54 ` Vlastimil Babka
2026-01-23 15:10 ` Lorenzo Stoakes
2026-01-22 13:01 ` [PATCH v3 06/10] mm/vma: clean up __vma_enter/exit_locked() Lorenzo Stoakes
2026-01-22 13:08 ` Lorenzo Stoakes
2026-01-22 20:15 ` Suren Baghdasaryan
2026-01-22 20:55 ` Andrew Morton
2026-01-23 16:15 ` Lorenzo Stoakes
2026-01-23 16:33 ` Lorenzo Stoakes
2026-01-23 9:16 ` Vlastimil Babka
2026-01-23 16:17 ` Lorenzo Stoakes
2026-01-23 16:28 ` Lorenzo Stoakes
2026-01-22 13:01 ` [PATCH RESEND v3 07/10] mm/vma: introduce helper struct + thread through exclusive lock fns Lorenzo Stoakes
2026-01-22 21:41 ` Suren Baghdasaryan
2026-01-23 17:59 ` Lorenzo Stoakes
2026-01-23 19:34 ` Suren Baghdasaryan
2026-01-23 20:04 ` Lorenzo Stoakes
2026-01-23 22:07 ` Suren Baghdasaryan
2026-01-24 8:54 ` Lorenzo Stoakes
2026-01-26 6:09 ` Suren Baghdasaryan
2026-01-23 10:02 ` Vlastimil Babka
2026-01-23 18:18 ` Lorenzo Stoakes
2026-01-22 13:02 ` [PATCH RESEND v3 08/10] mm/vma: improve and document __is_vma_write_locked() Lorenzo Stoakes
2026-01-22 21:55 ` Suren Baghdasaryan
2026-01-23 16:21 ` Vlastimil Babka
2026-01-23 17:42 ` Suren Baghdasaryan
2026-01-23 18:44 ` Lorenzo Stoakes
2026-01-22 13:02 ` [PATCH RESEND v3 09/10] mm/vma: update vma_assert_locked() to use lockdep Lorenzo Stoakes
2026-01-22 22:02 ` Suren Baghdasaryan
2026-01-23 18:45 ` Lorenzo Stoakes
2026-01-23 16:55 ` Vlastimil Babka
2026-01-23 18:49 ` Lorenzo Stoakes
2026-01-22 13:02 ` [PATCH RESEND v3 10/10] mm/vma: add and use vma_assert_stabilised() Lorenzo Stoakes
2026-01-22 22:12 ` Suren Baghdasaryan
2026-01-23 18:54 ` Lorenzo Stoakes
2026-01-23 17:10 ` Vlastimil Babka
2026-01-23 18:51 ` Lorenzo Stoakes
2026-01-23 23:35 ` Hillf Danton [this message]
2026-01-22 15:48 ` [PATCH RESEND v3 00/10] mm: add and use vma_assert_stabilised() helper Andrew Morton
2026-01-22 15:57 ` Lorenzo Stoakes
2026-01-22 16:01 ` Lorenzo Stoakes
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=20260123233550.2378-1-hdanton@sina.com \
--to=hdanton@sina.com \
--cc=akpm@linux-foundation.org \
--cc=bigeasy@linutronix.de \
--cc=boqun.feng@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=longman@redhat.com \
--cc=lorenzo.stoakes@oracle.com \
--cc=surenb@google.com \
/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