[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20260101225552.3423108-1-gthelen@google.com>
Date: Thu, 1 Jan 2026 14:55:51 -0800
From: Greg Thelen <gthelen@...gle.com>
To: Andrew Morton <akpm@...ux-foundation.org>, Shakeel Butt <shakeel.butt@...ux.dev>
Cc: linux-mm@...ck.org, linux-kernel@...r.kernel.org,
Greg Thelen <gthelen@...gle.com>
Subject: [PATCH] memcg-v1: remove folio_memcg_lock() doc reference
Commit a29c0e4b2e86 ("memcg-v1: remove memcg move locking code") removed
folio_memcg_lock(). Delete the final lingering documentation reference.
Fixes: a29c0e4b2e86 ("memcg-v1: remove memcg move locking code")
Signed-off-by: Greg Thelen <gthelen@...gle.com>
---
Documentation/admin-guide/cgroup-v1/memory.rst | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/Documentation/admin-guide/cgroup-v1/memory.rst b/Documentation/admin-guide/cgroup-v1/memory.rst
index d6b1db8cc7eb..7db63c002922 100644
--- a/Documentation/admin-guide/cgroup-v1/memory.rst
+++ b/Documentation/admin-guide/cgroup-v1/memory.rst
@@ -311,9 +311,8 @@ Lock order is as follows::
folio_lock
mm->page_table_lock or split pte_lock
- folio_memcg_lock (memcg->move_lock)
- mapping->i_pages lock
- lruvec->lru_lock.
+ mapping->i_pages lock
+ lruvec->lru_lock.
Per-node-per-memcgroup LRU (cgroup's private LRU) is guarded by
lruvec->lru_lock; the folio LRU flag is cleared before
--
2.52.0.358.g0dd7633a29-goog
Powered by blists - more mailing lists