mm-vma-introduce-helper-struct-thread-through-exclusive-lock-fns.patch removed from -mm tree
The quilt patch titled
Subject: mm/vma: introduce helper struct + thread through exclusive lock fns
has been removed from the -mm tree. Its filename was
mm-vma-introduce-helper-struct-thread-through-exclusive-lock-fns.patch
This patch was dropped because it was merged into the mm-stable branch of git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
------------------------------------------------------
From: Lorenzo Stoakes <[email protected]>
Subject: mm/vma: introduce helper struct + thread through exclusive lock fns
Date: Fri, 23 Jan 2026 20:12:17 +0000
It is confusing to have __vma_start_exclude_readers() return 0, 1 or an error (but only when waiting for readers in TASK_KILLABLE state), and having the return value be stored in a stack variable called 'locked' is further confusion.
More generally, we are doing a lot of rather finnicky things during the acquisition of a state in which readers are excluded and moving out of this state, including tracking whether we are detached or not or whether an error occurred.
We are implementing logic in __vma_start_exclude_readers() that effectively acts as if 'if one caller calls us do X, if another then do Y', which is very confusing from a control flow perspective.
Introducing the shared helper object state helps us avoid this, as we can now handle the 'an error arose but we're detached' condition correctly in both callers - a warning if not detaching, and treating the situation as if no error arose in the case of a VMA detaching.
This also acts to help document what's going on and allows us to add some more logical debug asserts.
Also update vma_mark_detached() to add a guard clause for the likely 'already detached' state (given we hold the mmap write lock), and add a comment about ephemeral VMA read lock reference count increments to clarify why we are entering/exiting an exclusive locked state here.
Finally, separate vma_mark_detached() into its fast-path component and make it inline, then place the slow path for excluding readers in mmap_lock.c.
No functional change intended.
---
include/linux/mm_types.h | 14 +-- include/linux/mmap_lock.h | 23 +++++ mm/mmap_lock.c | 158 +++++++++++++++++++----------------- 3 files changed, 115 insertions(+), 80 deletions(-)
include/linux/mmap_lock.h renamed from include/linux/mmap_lock.h~mm-vma-introduce-helper-struct-thread-through-exclusive-lock-fns +22 -1
@@ -358,7 +358,28 @@ static inline void vma_mark_attached(strrefcount_set_release (&vma->vm_refcnt,1 ); } -void vma_mark_detached (struct vm_area_struct *vma); +void __vma_exclude_readers_for_detach (struct vm_area_struct *vma); + +static inline void vma_mark_detached (struct vm_area_struct *vma) +{ +vma_assert_write_locked (vma); +vma_assert_attached (vma); + +/* +* The VMA still being attached (refcnt > 0) - is unlikely, because the +* vma has been already write-locked and readers can increment vm_refcnt +* only temporarily before they check vm_lock_seq, realize the vma is +* locked and drop back the vm_refcnt. That is a narrow window for +* observing a raised vm_refcnt. +* +* See the comment describing the vm_area_struct->vm_refcnt field for +* details of possible refcnt values. +*/ +if (likely (!__vma_refcount_put_return (vma))) +return ; + +__vma_exclude_readers_for_detach (vma); +}struct vm_area_struct *lock_vma_under_rcu (struct mm_struct *mm,unsigned long address);
include/linux/mm_types.h renamed from include/linux/mm_types.h~mm-vma-introduce-helper-struct-thread-through-exclusive-lock-fns +7 -7
@@ -1011,15 +1011,15 @@ struct vm_area_struct {* decrementing it again. * * VM_REFCNT_EXCLUDE_READERS_FLAG - Detached, pending -* __vma_exit_locked() completion which will decrement the reference -* count to zero. IMPORTANT - at this stage no further readers can -* increment the reference count. It can only be reduced. +* __vma_end_exclude_readers() completion which will decrement the +* reference count to zero. IMPORTANT - at this stage no further readers +* can increment the reference count. It can only be reduced. * * VM_REFCNT_EXCLUDE_READERS_FLAG + 1 - A thread is either write-locking -* an attached VMA and has yet to invoke __vma_exit_locked(), OR a -* thread is detaching a VMA and is waiting on a single spurious reader -* in order to decrement the reference count. IMPORTANT - as above, no -* further readers can increment the reference count. +* an attached VMA and has yet to invoke __vma_end_exclude_readers(), +* OR a thread is detaching a VMA and is waiting on a single spurious +* reader in order to decrement the reference count. IMPORTANT - as +* above, no further readers can increment the reference count. * * > VM_REFCNT_EXCLUDE_READERS_FLAG + 1 - A thread is either * write-locking or detaching a VMA is waiting on readers to
mm/mmap_lock.c renamed from mm/mmap_lock.c~mm-vma-introduce-helper-struct-thread-through-exclusive-lock-fns +86 -72
220 lines not on this page · raw message
_
Patches currently in -mm which might be from [email protected] are
mm-vma-remove-__private-sparse-decoration-from-vma_flags_t.patch mm-rename-vma_flag_test-set_atomic-to-vma_test-set_atomic_flag.patch mm-add-mk_vma_flags-bitmap-flag-macro-helper.patch tools-bitmap-add-missing-bitmap_.patch mm-add-basic-vma-flag-operation-helper-functions.patch mm-update-hugetlbfs-to-use-vma-flags-on-mmap_prepare.patch mm-update-secretmem-to-use-vma-flags-on-mmap_prepare.patch mm-update-secretmem-to-use-vma-flags-on-mmap_prepare-fix.patch mm-update-shmem__file_-functions-to-use-vma_flags_t.patch mm-update-all-remaining-mmap_prepare-users-to-use-vma_flags_t.patch mm-make-vm_area_desc-utilise-vma_flags_t-only.patch tools-testing-vma-separate-vma-userland-tests-into-separate-files.patch tools-testing-vma-separate-out-vma_internalh-into-logical-headers.patch tools-testing-vma-separate-out-vma_internalh-into-logical-headers-fix.patch tools-testing-vma-add-vma-userland-tests-for-vma-flag-functions.patch