Skip to contentSkip to conversation

memcg-v1: remove folio_memcg_lock() doc reference

PATCH Applied Greg Thelen 3 participants 3 messages Jan 1 – Jan 2

Subsystems (3)
lore
Share & tools
lore
#0 lore raw

PATCH 1/1 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")
---
 Documentation/admin-guide/cgroup-v1/memory.rst | 5 ++---
 1 file changed, 2 insertions(+), 3 deletions(-)
Documentation/admin-guide/cgroup-v1/memory.rst +2 -3
index d6b1db8cc7eb..7db63c002922 100644
@@ -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
Signature · 1 line
2.52.0.358.g0dd7633a29-goog
Acked-by on v1 1/1
#2 lore raw
In reply to Greg Thelen
Quoted 2 lines · On Thu, 1 Jan 2026 14:55:51 -0800 Greg Thelen <[email protected]> wrote:

Commit a29c0e4b2e86 ("memcg-v1: remove memcg move locking code") removed folio_memcg_lock(). Delete the final lingering documentation reference.

Nice cleanup!

Quoted 3 lines
Fixes a29c0e4b2e86 ("memcg-v1: remove memcg move locking code")

Thanks,
SJ

[...]