From: Deepanshu Kartikey <kartikey406@gmail.com>
To: akpm@linux-foundation.org, axelrasmussen@google.com,
yuanchu@google.com, weixugc@google.com, hannes@cmpxchg.org,
david@kernel.org, mhocko@kernel.org, zhengqi.arch@bytedance.com,
shakeel.butt@linux.dev, lorenzo.stoakes@oracle.com,
yuzhao@google.com, heftig@archlinux.org,
oleksandr@natalenko.name, bgeffon@google.com
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Deepanshu Kartikey <kartikey406@gmail.com>,
syzbot+90fcab4d88cffed6d0d8@syzkaller.appspotmail.com
Subject: [PATCH] mm: vmscan: always allow writeback during memcg reclaim
Date: Sat, 13 Dec 2025 14:06:39 +0530 [thread overview]
Message-ID: <20251213083639.364539-1-kartikey406@gmail.com> (raw)
When laptop_mode is enabled, may_writepage is set to 0 in
try_to_free_mem_cgroup_pages(). This triggers a warning in MGLRU's
lru_gen_shrink_lruvec():
VM_WARN_ON_ONCE(!sc->may_writepage || !sc->may_unmap);
The warning occurs because MGLRU expects full reclaim capabilities to
function correctly. The call path is:
mem_cgroup_resize_max()
try_to_free_mem_cgroup_pages()
do_try_to_free_pages()
shrink_node()
shrink_lruvec()
lru_gen_shrink_lruvec() <-- WARNING
Unlike kswapd or direct reclaim where laptop_mode's disk-saving behavior
is a reasonable optimization, memcg limit enforcement is a hard
requirement - memory MUST be freed when a cgroup exceeds its limit.
The may_unmap field is already set unconditionally to 1 in this path,
acknowledging that memcg reclaim needs full capabilities.
Set may_writepage unconditionally to 1 for memcg reclaim to ensure
MGLRU works correctly and memory limits are properly enforced.
Fixes: bd74fdaea146 ("mm: multi-gen LRU: support page table walks")
Reported-by: syzbot+90fcab4d88cffed6d0d8@syzkaller.appspotmail.com
Closes: https://syzkaller.appspot.com/bug?extid=90fcab4d88cffed6d0d8
Signed-off-by: Deepanshu Kartikey <kartikey406@gmail.com>
---
Note: Only compile-tested. No reproducer available from syzbot.
---
mm/vmscan.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/mm/vmscan.c b/mm/vmscan.c
index 900c74b6aa62..5e1c99d9cbd7 100644
--- a/mm/vmscan.c
+++ b/mm/vmscan.c
@@ -6669,7 +6669,7 @@ unsigned long try_to_free_mem_cgroup_pages(struct mem_cgroup *memcg,
.reclaim_idx = MAX_NR_ZONES - 1,
.target_mem_cgroup = memcg,
.priority = DEF_PRIORITY,
- .may_writepage = !laptop_mode,
+ .may_writepage = 1,
.may_unmap = 1,
.may_swap = !!(reclaim_options & MEMCG_RECLAIM_MAY_SWAP),
.proactive = !!(reclaim_options & MEMCG_RECLAIM_PROACTIVE),
--
2.43.0
next reply other threads:[~2025-12-13 8:36 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-13 8:36 Deepanshu Kartikey [this message]
2025-12-14 23:49 ` Andrew Morton
2025-12-15 4:12 ` Johannes Weiner
2025-12-15 4:51 ` Deepanshu Kartikey
2025-12-15 19:42 ` Yuanchu Xie
2025-12-15 20:22 ` Johannes Weiner
2025-12-19 5:13 ` Kairui Song
2025-12-15 6:59 ` retiring laptop_mode? was " Christoph Hellwig
2025-12-15 16:33 ` Jens Axboe
2025-12-15 20:08 ` Johannes Weiner
2025-12-16 2:23 ` Jens Axboe
2025-12-16 7:41 ` Christoph Hellwig
2025-12-16 18:52 ` Johannes Weiner
2025-12-16 18:54 ` Jens Axboe
2025-12-16 23:23 ` Shakeel Butt
2025-12-17 19:59 ` Johannes Weiner
2025-12-18 7:21 ` Shakeel Butt
2025-12-17 19:34 ` Michal Hocko
2025-12-18 6:00 ` Christoph Hellwig
2025-12-15 17:49 ` Michal Hocko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20251213083639.364539-1-kartikey406@gmail.com \
--to=kartikey406@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=axelrasmussen@google.com \
--cc=bgeffon@google.com \
--cc=david@kernel.org \
--cc=hannes@cmpxchg.org \
--cc=heftig@archlinux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=mhocko@kernel.org \
--cc=oleksandr@natalenko.name \
--cc=shakeel.butt@linux.dev \
--cc=syzbot+90fcab4d88cffed6d0d8@syzkaller.appspotmail.com \
--cc=weixugc@google.com \
--cc=yuanchu@google.com \
--cc=yuzhao@google.com \
--cc=zhengqi.arch@bytedance.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox