From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from out30-100.freemail.mail.aliyun.com (out30-100.freemail.mail.aliyun.com [115.124.30.100]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id B4BCD3BCD26 for ; Wed, 12 Aug 2026 08:29:54 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=115.124.30.100 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1786523398; cv=none; b=SuIY/Y5n4syZJs3IAuc3sLx052WY9hnGVYvGTs5kqwLFAvDwqp6FZBC1ogUEZQYOZwQHiw5nT7AJ+4qwDQl8YDytxP5Hh5Bdh3Wz+SxQoueDWWcrn8kvDQzI933Hc8rBZbrbUvmLglTAxvUqQ3ptG/8W9IxLaaSewYGEyHd7Vd0= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1786523398; c=relaxed/simple; bh=bwYI4QNGMc0h/ek65O2LSLHEGJr5yw7ak0EEsPJakyw=; h=Message-ID:Date:MIME-Version:Subject:To:Cc:References:From: In-Reply-To:Content-Type; b=bJ7WdXz+f7ylfBFnck7uBO8QWoQvdy32oryGT+tMJ5vhWbIS0HlV3QQOhFC6bsapv5FcV0OVr4ygzm3oc/P8SryRzqFbG53mIOu/euwEAAAk6wVf32jjCwR+5seYp2PLOhx2Db+s9nlswBuv3QFeskocpiOsO3zxevUJNry6XZg= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.alibaba.com; spf=pass smtp.mailfrom=linux.alibaba.com; dkim=pass (1024-bit key) header.d=linux.alibaba.com header.i=@linux.alibaba.com header.b=d53t9GUL; arc=none smtp.client-ip=115.124.30.100 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.alibaba.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=linux.alibaba.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linux.alibaba.com header.i=@linux.alibaba.com header.b="d53t9GUL" DKIM-Signature:v=1; a=rsa-sha256; c=relaxed/relaxed; d=linux.alibaba.com; s=default; t=1786523386; h=Message-ID:Date:MIME-Version:Subject:To:From:Content-Type; bh=sKaJ6FGtUdSwXT7P2z1g+Pgsj1kf9fIfFELLU/0C2V4=; b=d53t9GULhYnouL3Y68xmmQTG72nCbKxaVw9I0q4gctK25532VORyhxRL6blIUxojnwmzxKiYH/w7X3Hm7FesaLK933qZ75LJIgymdNDUjtj7M1BCgqoStHLQld4Zst7arFLxr8/sq/mg6BqazMe9GECvPupUA4m4YEtx5uLUzHI= X-Alimail-AntiSpam:AC=PASS;BC=-1|-1;BR=01201311R111e4;CH=green;DM=||false|;DS=||;FP=0|-1|-1|-1|0|-1|-1|-1;HT=maildocker-contentspam033037009110;MF=baolin.wang@linux.alibaba.com;NM=1;PH=DS;RN=16;SR=0;TI=SMTPD_---0X8r1lbl_1786523383; Received: from 30.74.144.118(mailfrom:baolin.wang@linux.alibaba.com fp:SMTPD_---0X8r1lbl_1786523383 cluster:ay36) by smtp.aliyun-inc.com; Wed, 12 Aug 2026 16:29:44 +0800 Message-ID: <88ed8a93-ae55-4281-b99d-ec4a6b6a2deb@linux.alibaba.com> Date: Wed, 12 Aug 2026 16:29:42 +0800 Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [syzbot] [mm?] WARNING in set_mm_walk To: Shakeel Butt , Andrew Morton Cc: syzbot , axelrasmussen@google.com, baohua@kernel.org, david@kernel.org, hannes@cmpxchg.org, kasong@tencent.com, linux-kernel@vger.kernel.org, linux-mm@kvack.org, ljs@kernel.org, mhocko@kernel.org, qi.zheng@linux.dev, syzkaller-bugs@googlegroups.com, weixugc@google.com, Yuanchu Xie References: <6a7a6929.b50370da.49fe0.005e.GAE@google.com> <20260810174852.aca0f73ab7ad71c70dcdefda@linux-foundation.org> From: Baolin Wang In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit On 8/11/26 12:39 PM, Shakeel Butt wrote: > On Mon, Aug 10, 2026 at 05:48:52PM -0700, Andrew Morton wrote: >> On Mon, 10 Aug 2026 17:13:29 -0700 syzbot wrote: >> >>> Hello, >>> >>> syzbot found the following issue on: >>> >>> HEAD commit: 562bfb501c54 Merge tag 'integrity-v7.2-rc7' of git://git.k.. >>> git tree: upstream >>> console output: https://syzkaller.appspot.com/x/log.txt?x=11a8cbb9580000 >>> kernel config: https://syzkaller.appspot.com/x/.config?x=145fa60d73086782 >>> dashboard link: https://syzkaller.appspot.com/bug?extid=12ee2725d5fde63a9c96 >>> compiler: gcc (Debian 14.2.0-19) 14.2.0, GNU ld (GNU Binutils for Debian) 2.44 >> >> Thanks. One for the MGLRU develoeprs, it seems. >> >> https://share.gemini.google/Wg4a5ns7E0LF might save a bit of time figuring this out. >> > > This is memcg-v1's soft limit which is deprecated. I am more inclined to simply > remove this code instead of fixing it. > > I will take a stab at removal. MGLRU doesn't actually support memcg-v1's soft limit: unsigned long memcg1_soft_limit_reclaim(pg_data_t *pgdat, int order, gfp_t gfp_mask, unsigned long *total_scanned) { ...... if (lru_gen_enabled()) return 0; ...... } The call trace below likely showed up because the test repeatedly toggled MGLRU on and off, which isn't a normal operation and should be avoided in practice. I also agree that removing the deprecated memcg-v1 soft limit is the better way forward. >>> Unfortunately, I don't have any reproducer for this issue yet. >>> >>> Downloadable assets: >>> disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/d900f083ada3/non_bootable_disk-562bfb50.raw.xz >>> vmlinux: https://storage.googleapis.com/syzbot-assets/9cbf6ef0490e/vmlinux-562bfb50.xz >>> kernel image: https://storage.googleapis.com/syzbot-assets/7ee52864c79a/bzImage-562bfb50.xz >>> >>> IMPORTANT: if you fix the issue, please add the following tag to the commit: >>> Reported-by: syzbot+12ee2725d5fde63a9c96@syzkaller.appspotmail.com >>> >>> ------------[ cut here ]------------ >>> current_is_kswapd() >>> WARNING: mm/vmscan.c:3800 at set_mm_walk+0x210/0x270 mm/vmscan.c:3800, CPU#1: kswapd0/110 >>> >>> Modules linked in: >>> CPU: 1 UID: 0 PID: 110 Comm: kswapd0 Tainted: G L syzkaller #0 PREEMPT(full) >>> Tainted: [L]=SOFTLOCKUP >>> Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 >>> RIP: 0010:set_mm_walk+0x210/0x270 mm/vmscan.c:3800 >>> Code: 13 00 00 4d 8d 7d 08 e9 f7 fe ff ff e8 79 f5 2a 00 e9 b7 fe ff ff e8 7f 6b ba ff 90 0f 0b 90 e9 d2 fe ff ff e8 71 6b ba ff 90 <0f> 0b 90 e9 74 ff ff ff 4c 89 ff e8 80 f5 2a 00 e9 4e fe ff ff 48 >>> RSP: 0018:ffffc900027772b8 EFLAGS: 00010293 >>> RAX: 0000000000000000 RBX: ffff888024934a80 RCX: ffffffff824ff8e8 >>> RDX: ffff888024934a80 RSI: ffffffff824ff96f RDI: ffff888024934a80 >>> RBP: 0000000000020000 R08: 0000000000000005 R09: 0000000000000000 >>> R10: 0000000000020000 R11: 0000000000000000 R12: 0000000000000000 >>> R13: ffffc90002777c38 R14: 0000000000000001 R15: ffffc90002777c40 >>> FS: 0000000000000000(0000) GS:ffff8880d5ed8000(0000) knlGS:0000000000000000 >>> CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 >>> CR2: 0000001b31923ffc CR3: 0000000109695000 CR4: 0000000000352ef0 >>> DR0: 0000000000000005 DR1: 0000000000000005 DR2: 0000000020040004 >>> DR3: 0000000000000056 DR6: 00000000ffff0ff0 DR7: 0000000000000400 >>> Call Trace: >>> >>> try_to_inc_max_seq+0xf0/0x1090 mm/vmscan.c:4023 >>> try_to_shrink_lruvec+0x4bd/0x6b0 mm/vmscan.c:4977 >>> lru_gen_shrink_lruvec mm/vmscan.c:5128 [inline] >>> shrink_lruvec+0x31e/0x25b0 mm/vmscan.c:5888 >>> mem_cgroup_shrink_node+0x227/0x6a0 mm/vmscan.c:6753 >>> mem_cgroup_soft_reclaim mm/memcontrol-v1.c:312 [inline] >>> memcg1_soft_limit_reclaim+0x2d5/0x830 mm/memcontrol-v1.c:362 >>> balance_pgdat+0xa11/0x1f00 mm/vmscan.c:7177 >>> kswapd+0x556/0xb50 mm/vmscan.c:7462 >>> kthread+0x370/0x450 kernel/kthread.c:436 >>> ret_from_fork+0x72b/0xd50 arch/x86/kernel/process.c:158 >>> ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245 >>> >>> >>> >>> --- >>> This report is generated by a bot. It may contain errors. >>> See https://goo.gl/tpsmEJ for more information about syzbot. >>> syzbot engineers can be reached at syzkaller@googlegroups.com. >>> >>> syzbot will keep track of this issue. See: >>> https://goo.gl/tpsmEJ#status for how to communicate with syzbot. >>> >>> If the report is already addressed, let syzbot know by replying with: >>> #syz fix: exact-commit-title >>> >>> If you want to overwrite report's subsystems, reply with: >>> #syz set subsystems: new-subsystem >>> (See the list of subsystem names on the web dashboard) >>> >>> If the report is a duplicate of another one, reply with: >>> #syz dup: exact-subject-of-another-report >>> >>> If you want to undo deduplication, reply with: >>> #syz undup