Skip to contentSkip to conversation

mm-memcg-mz-already-removed-from-rb_tree-if-not-null.patch removed from -mm tree

merged mm-stable Andrew Morton 1 participant 1 message May 10, 2022

lore
Share & tools
lore

Andrew Morton

author tree notice Applied
#0 lore raw

The quilt patch titled
Subject: mm/memcg: mz already removed from rb_tree if not NULL
has been removed from the -mm tree. Its filename was
mm-memcg-mz-already-removed-from-rb_tree-if-not-null.patch

This patch was dropped because it was merged into mm-stable

------------------------------------------------------
From: Wei Yang <[email protected]>
Subject: mm/memcg: mz already removed from rb_tree if not NULL

When mz is not NULL, it means mz can either come from mem_cgroup_largest_soft_limit_node or __mem_cgroup_largest_soft_limit_node. And both of them have removed this node by __mem_cgroup_remove_exceeded().

Not necessary to call __mem_cgroup_remove_exceeded() again.

---

 mm/memcontrol.c |    1 -
 1 file changed, 1 deletion(-)
mm/memcontrol.c renamed from mm/memcontrol.c~mm-memcg-mz-already-removed-from-rb_tree-if-not-null +0 -1
@@ -3418,7 +3418,6 @@ unsigned long mem_cgroup_soft_limit_recl
 						    gfp_mask, total_scanned);
 		nr_reclaimed += reclaimed;
 		spin_lock_irq(&mctz->lock);
-		__mem_cgroup_remove_exceeded(mz, mctz);
 
 		/*
 		 * If we failed to reclaim anything from this memory cgroup

_

Patches currently in -mm which might be from [email protected] are

mm-vmscan-not-necessary-to-re-init-the-list-for-each-iteration.patch mm-vmscan-filter-empty-page_list-at-the-beginning.patch mm-vmscan-not-use-numa_no_node-as-indicator-of-page-on-different-node.patch