mm-swap-strengthen-locking-assertions-and-invariants-in-cluster-allocation.patch removed from -mm tree
The quilt patch titled
Subject: mm/swap: strengthen locking assertions and invariants in cluster allocation
has been removed from the -mm tree. Its filename was
mm-swap-strengthen-locking-assertions-and-invariants-in-cluster-allocation.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: Hui Zhu <[email protected]>
Subject: mm/swap: strengthen locking assertions and invariants in cluster allocation
Date: Tue, 10 Mar 2026 09:56:57 +0800
swap_cluster_alloc_table() requires several locks to be held by its
callers: ci->lock, the per-CPU swap_cluster lock, and, for non-solid-state devices (non-SWP_SOLIDSTATE), the si->global_cluster_lock.
While most call paths (e.g., via cluster_alloc_swap_entry() or alloc_swap_scan_list()) correctly acquire these locks before invocation, the path through swap_reclaim_work() -> swap_reclaim_full_clusters() -> isolate_lock_cluster() is distinct. This path operates exclusively on si->full_clusters, where the swap allocation tables are guaranteed to be already allocated. Consequently, isolate_lock_cluster() should never trigger a call to swap_cluster_alloc_table() for these clusters.
Strengthen the locking and state assertions to formalize these invariants:
1. Add a lockdep_assert_held() for si->global_cluster_lock in swap_cluster_alloc_table() for non-SWP_SOLIDSTATE devices.
2. Reorder existing lockdep assertions in swap_cluster_alloc_table() to match the actual lock acquisition order (per-CPU lock, then global lock, then cluster lock).
3. Add a VM_WARN_ON_ONCE() in isolate_lock_cluster() to ensure that table allocations are only attempted for clusters being isolated from the free list. Attempting to allocate a table for a cluster from other lists (like the full list during reclaim) indicates a violation of subsystem invariants.
These changes ensure locking consistency and help catch potential synchronization or logic issues during development.
---
mm/swapfile.c | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-)
mm/swapfile.c renamed from mm/swapfile.c~mm-swap-strengthen-locking-assertions-and-invariants-in-cluster-allocation +6 -1
@@ -498,8 +498,10 @@ swap_cluster_alloc_table(struct swap_inf* Only cluster isolation from the allocator does table allocation. * Swap allocator uses percpu clusters and holds the local lock. */ -lockdep_assert_held (&ci->lock);lockdep_assert_held (&this_cpu_ptr (&percpu_swap_cluster)->lock); +if (!(si->flags &SWP_SOLIDSTATE )) +lockdep_assert_held (&si->global_cluster_lock); +lockdep_assert_held (&ci->lock);/* The cluster must be free and was just isolated from the free list. */ VM_WARN_ON_ONCE (ci->flags || !cluster_is_empty (ci));
@@ -600,6 +602,7 @@ static struct swap_cluster_info *isolate struct swap_info_struct *si, struct list_head *list) { struct swap_cluster_info *ci, *found = NULL; +u8 flags =CLUSTER_FLAG_NONE ;spin_lock (&si->lock);list_for_each_entry (ci, list, list) {
@@ -612,6 +615,7 @@ static struct swap_cluster_info *isolate ci->flags != CLUSTER_FLAG_FULL);list_del (&ci->list); + flags = ci->flags; ci->flags =CLUSTER_FLAG_NONE ; found = ci;break ;
@@ -620,6 +624,7 @@ static struct swap_cluster_info *isolateif (found && !cluster_table_is_alloced (found)) {/* Only an empty free cluster's swap table can be freed. */ +VM_WARN_ON_ONCE (flags !=CLUSTER_FLAG_FREE );VM_WARN_ON_ONCE (list != &si->free_clusters);VM_WARN_ON_ONCE (!cluster_is_empty (found));return swap_cluster_alloc_table (si, found);
_
Patches currently in -mm which might be from [email protected] are
mm-memcontrol-batch-memcg-charging-in-__memcg_slab_post_alloc_hook.patch