From: syzbot <syzbot+079a3b213add54dd18a7@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Forwarded: [PATCH] mm/vmscan: test build to verify VM_WARN_ON_ONCE fix
Date: Sat, 17 Jan 2026 21:02:46 -0800 [thread overview]
Message-ID: <696c6976.a70a0220.34546f.0224.GAE@google.com> (raw)
In-Reply-To: <696b56b1.050a0220.3390f1.0007.GAE@google.com>
For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.
***
Subject: [PATCH] mm/vmscan: test build to verify VM_WARN_ON_ONCE fix
Author: kartikey406@gmail.com
#syz test: git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
Test build to verify that VM_WARN_ON_ONCE in memcg1_swapout() no
longer triggers after Kairui Song's reordering patch.
This is a local test commit only and should NOT be submitted upstream.
Signed-off-by: Deepanshu Kartikey <kartikey406@gmail.com>
---
mm/vmscan.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/mm/vmscan.c b/mm/vmscan.c
index a0e3f51de749..ac8cffddc2ea 100644
--- a/mm/vmscan.c
+++ b/mm/vmscan.c
@@ -760,6 +760,7 @@ static int __remove_mapping(struct address_space *mapping, struct folio *folio,
if (reclaimed && !mapping_exiting(mapping))
shadow = workingset_eviction(folio, target_memcg);
+
memcg1_swapout(folio, swap);
__swap_cache_del_folio(ci, folio, swap, shadow);
swap_cluster_unlock_irq(ci);
--
2.43.0
prev parent reply other threads:[~2026-01-18 5:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-17 9:30 [syzbot] [cgroups?] [mm?] WARNING in memcg1_swapout syzbot
2026-01-18 0:57 ` Andrew Morton
2026-01-18 4:21 ` Deepanshu Kartikey
2026-01-18 7:01 ` Deepanshu Kartikey
2026-01-18 20:53 ` Andrew Morton
2026-01-20 21:20 ` Shakeel Butt
2026-01-21 14:58 ` Johannes Weiner
2026-01-21 16:35 ` Andrew Morton
2026-01-21 17:01 ` Johannes Weiner
2026-01-18 5:02 ` syzbot [this message]
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=696c6976.a70a0220.34546f.0224.GAE@google.com \
--to=syzbot+079a3b213add54dd18a7@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.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
Powered by JetHome