* [syzbot ci] Re: mm/mglru: frequency guided promotion (MGLRU-FG) and flag cleanup [not found] <20260804-mglru-fg-v1-0-4d8dad39dad6@tencent.com> @ 2026-08-04 5:26 ` syzbot ci 2026-08-04 5:56 ` Kairui Song 0 siblings, 1 reply; 2+ messages in thread From: syzbot ci @ 2026-08-04 5:26 UTC (permalink / raw) To: akpm, axelrasmussen, baohua, baolin.wang, baoquan.he, cgroups, chenridong, chrisl, david, dev.jain, devnull, gourry, hannes, hughd, kasong, lance.yang, linux-kernel, linux-mm, ljs, mhocko, muchun.song, nico.pache, nphamcs, qi.zheng, rientjes, roman.gushchin, ryan.roberts, ryncsn, shakeel.butt, shikemeng, sj, surenb, tz2294, usama.arif, vbabka, vernon2gm, wangzicheng, weixugc, willy, ying.huang, youngjun.park, yuanchu, yuzhao, ziy Cc: syzbot, syzkaller-bugs syzbot ci has tested the following series [v1] mm/mglru: frequency guided promotion (MGLRU-FG) and flag cleanup https://lore.kernel.org/all/20260804-mglru-fg-v1-0-4d8dad39dad6@tencent.com * [PATCH RFC 01/15] mm/memcontrol: make lru_zone_size atomic and simplify sanity check * [PATCH RFC 02/15] mm/memcontrol: allow update of LRU statistic without holding LRU lock * [PATCH RFC 03/15] mm/mglru: introduce and always use helpers for manipulating page flags * [PATCH RFC 04/15] mm/mglru: make generation page counters atomic * [PATCH RFC 05/15] mm/mglru: move max_seq read into walk_update_folio * [PATCH RFC 06/15] mm/mglru: use explicit tier range in read_ctrl_pos() * [PATCH RFC 07/15] mm/mglru: move refault workingset activation into lru_gen_refault * [PATCH RFC 08/15] mm/memcg: add folio-based lruvec live helper * [PATCH RFC 09/15] mm/mglru: frequency guided workingset promotion (MGLRU-FG) * [PATCH RFC 10/15] mm/mglru: make folio lru referenced times count a generic API * [PATCH RFC 11/15] mm/mglru: replace folio workinset check and update with new helper * [PATCH RFC 12/15] mm/smap: report workingset folios as referenced * [PATCH RFC 13/15] mm/huge_memory: mark file folio as accessed more accurately on split * [PATCH RFC 14/15] mm/khugepaged: consider workingset folios as referenced * [PATCH RFC 15/15] mm/madvise: convert to new lru refs API and better support for MGLRU and found the following issue: WARNING in folio_inc_lru_refs Full report is available here: https://ci.syzbot.org/series/5db36d1d-9faa-4882-9f0d-1a8f52132274 *** WARNING in folio_inc_lru_refs tree: mm-new URL: https://kernel.googlesource.com/pub/scm/linux/kernel/git/akpm/mm.git base: 94f9b3980dd446b56acf1dfed649e9b32a9f3813 arch: amd64 compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8 config: https://ci.syzbot.org/builds/9f324367-2b95-4fd0-9025-fef1ff1f605a/config page: refcount:3 mapcount:2 mapping:0000000000000000 index:0x0 pfn:0xe4ee flags: 0xfff00000002000(reserved|node=0|zone=1|lastcpupid=0x7ff) raw: 00fff00000002000 ffffea0000393b88 ffffea0000393b88 0000000000000000 raw: 0000000000000000 0000000000000000 0000000300000001 0000000000000000 page dumped because: VM_WARN_ON_ONCE_FOLIO(!memcg && !mem_cgroup_disabled()) page_owner info is not present (never set?) ------------[ cut here ]------------ 1 WARNING: ./include/linux/memcontrol.h:745 at folio_inc_lru_refs+0xb4f/0xc10, CPU#0: mount/5025 Modules linked in: CPU: 0 UID: 0 PID: 5025 Comm: mount Not tainted syzkaller #0 PREEMPT(full) Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.2-debian-1.16.2-1 04/01/2014 RIP: 0010:folio_inc_lru_refs+0xb4f/0xc10 Code: ff 4c 89 e7 e8 c2 ae fd ff e9 e9 fc ff ff e8 18 91 ba ff 4c 89 e7 48 c7 c6 20 90 f8 8b e8 99 b0 1b ff c6 05 a6 a9 34 0e 01 90 <0f> 0b 90 e9 85 f6 ff ff e8 f4 90 ba ff e9 29 f8 ff ff 44 89 f1 80 RSP: 0018:ffffc9000324f4c0 EFLAGS: 00010246 RAX: 8e914a919570c700 RBX: 0000000000000000 RCX: 0000000000000001 RDX: 0000000000000000 RSI: ffffffff8e4b4187 RDI: ffff888174f53c00 RBP: ffffc9000324f5d0 R08: 0000000000000003 R09: 0000000000000004 R10: dffffc0000000000 R11: fffffbfff1d3ca24 R12: ffffea0000393b80 R13: 1ffffd4000072770 R14: 1ffff92000649ea8 R15: dffffc0000000000 FS: 0000000000000000(0000) GS:ffff88818d949000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007fb77b215440 CR3: 000000000e946000 CR4: 00000000000006f0 Call Trace: <TASK> __zap_vma_range+0x20f5/0x4f70 unmap_vmas+0x390/0x550 exit_mmap+0x293/0x9f0 __mmput+0x118/0x420 exit_mm+0x221/0x2d0 do_exit+0x6cd/0x2360 do_group_exit+0x22d/0x2f0 __x64_sys_exit_group+0x3f/0x40 x64_sys_call+0x221a/0x2240 do_syscall_64+0x174/0x580 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7fb77b2d3a90 Code: Unable to access opcode bytes at 0x7fb77b2d3a66. RSP: 002b:00007ffe32d58618 EFLAGS: 00000246 ORIG_RAX: 00000000000000e7 RAX: ffffffffffffffda RBX: 00007fb77b3c4860 RCX: 00007fb77b2d3a90 RDX: 00000000000000e7 RSI: 000000000000003c RDI: 0000000000000000 RBP: 00007fb77b3c4860 R08: 00007ffe32d58490 R09: 00007ffe32d58570 R10: 00007ffe32d584d0 R11: 0000000000000246 R12: 0000000000000000 R13: 0000000000000000 R14: 00007fb77b3c8658 R15: 0000000000000001 </TASK> *** If these findings have caused you to resend the series or submit a separate fix, please add the following tag to your commit message: Tested-by: syzbot@syzkaller.appspotmail.com --- This report is generated by a bot. It may contain errors. syzbot ci engineers can be reached at syzkaller@googlegroups.com. To test a patch for this bug, please reply with `#syz test` (should be on a separate line). The patch should be attached to the email. Note: arguments like custom git repos and branches are not supported. ^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [syzbot ci] Re: mm/mglru: frequency guided promotion (MGLRU-FG) and flag cleanup 2026-08-04 5:26 ` [syzbot ci] Re: mm/mglru: frequency guided promotion (MGLRU-FG) and flag cleanup syzbot ci @ 2026-08-04 5:56 ` Kairui Song 0 siblings, 0 replies; 2+ messages in thread From: Kairui Song @ 2026-08-04 5:56 UTC (permalink / raw) To: syzbot ci Cc: akpm, axelrasmussen, baohua, baolin.wang, baoquan.he, cgroups, chenridong, chrisl, david, dev.jain, devnull, gourry, hannes, hughd, kasong, lance.yang, linux-kernel, linux-mm, ljs, mhocko, muchun.song, nico.pache, nphamcs, qi.zheng, rientjes, roman.gushchin, ryan.roberts, shakeel.butt, shikemeng, sj, surenb, tz2294, usama.arif, vbabka, vernon2gm, wangzicheng, weixugc, willy, ying.huang, youngjun.park, yuanchu, yuzhao, ziy, syzbot, syzkaller-bugs On Mon, Aug 03, 2026 at 10:26:17PM +0800, syzbot ci wrote: > syzbot ci has tested the following series > > [v1] mm/mglru: frequency guided promotion (MGLRU-FG) and flag cleanup > https://lore.kernel.org/all/20260804-mglru-fg-v1-0-4d8dad39dad6@tencent.com > * [PATCH RFC 01/15] mm/memcontrol: make lru_zone_size atomic and simplify sanity check > * [PATCH RFC 02/15] mm/memcontrol: allow update of LRU statistic without holding LRU lock > * [PATCH RFC 03/15] mm/mglru: introduce and always use helpers for manipulating page flags > * [PATCH RFC 04/15] mm/mglru: make generation page counters atomic > * [PATCH RFC 05/15] mm/mglru: move max_seq read into walk_update_folio > * [PATCH RFC 06/15] mm/mglru: use explicit tier range in read_ctrl_pos() > * [PATCH RFC 07/15] mm/mglru: move refault workingset activation into lru_gen_refault > * [PATCH RFC 08/15] mm/memcg: add folio-based lruvec live helper > * [PATCH RFC 09/15] mm/mglru: frequency guided workingset promotion (MGLRU-FG) > * [PATCH RFC 10/15] mm/mglru: make folio lru referenced times count a generic API > * [PATCH RFC 11/15] mm/mglru: replace folio workinset check and update with new helper > * [PATCH RFC 12/15] mm/smap: report workingset folios as referenced > * [PATCH RFC 13/15] mm/huge_memory: mark file folio as accessed more accurately on split > * [PATCH RFC 14/15] mm/khugepaged: consider workingset folios as referenced > * [PATCH RFC 15/15] mm/madvise: convert to new lru refs API and better support for MGLRU > > and found the following issue: > WARNING in folio_inc_lru_refs > > Full report is available here: > https://ci.syzbot.org/series/5db36d1d-9faa-4882-9f0d-1a8f52132274 > > *** > > WARNING in folio_inc_lru_refs > > tree: mm-new > URL: https://kernel.googlesource.com/pub/scm/linux/kernel/git/akpm/mm.git > base: 94f9b3980dd446b56acf1dfed649e9b32a9f3813 > arch: amd64 > compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8 > config: https://ci.syzbot.org/builds/9f324367-2b95-4fd0-9025-fef1ff1f605a/config > > page: refcount:3 mapcount:2 mapping:0000000000000000 index:0x0 pfn:0xe4ee > flags: 0xfff00000002000(reserved|node=0|zone=1|lastcpupid=0x7ff) > raw: 00fff00000002000 ffffea0000393b88 ffffea0000393b88 0000000000000000 > raw: 0000000000000000 0000000000000000 0000000300000001 0000000000000000 > page dumped because: VM_WARN_ON_ONCE_FOLIO(!memcg && !mem_cgroup_disabled()) > page_owner info is not present (never set?) > ------------[ cut here ]------------ > 1 > WARNING: ./include/linux/memcontrol.h:745 at folio_inc_lru_refs+0xb4f/0xc10, CPU#0: mount/5025 > Modules linked in: > CPU: 0 UID: 0 PID: 5025 Comm: mount Not tainted syzkaller #0 PREEMPT(full) > Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.2-debian-1.16.2-1 04/01/2014 > RIP: 0010:folio_inc_lru_refs+0xb4f/0xc10 > Code: ff 4c 89 e7 e8 c2 ae fd ff e9 e9 fc ff ff e8 18 91 ba ff 4c 89 e7 48 c7 c6 20 90 f8 8b e8 99 b0 1b ff c6 05 a6 a9 34 0e 01 90 <0f> 0b 90 e9 85 f6 ff ff e8 f4 90 ba ff e9 29 f8 ff ff 44 89 f1 80 > RSP: 0018:ffffc9000324f4c0 EFLAGS: 00010246 > RAX: 8e914a919570c700 RBX: 0000000000000000 RCX: 0000000000000001 > RDX: 0000000000000000 RSI: ffffffff8e4b4187 RDI: ffff888174f53c00 > RBP: ffffc9000324f5d0 R08: 0000000000000003 R09: 0000000000000004 > R10: dffffc0000000000 R11: fffffbfff1d3ca24 R12: ffffea0000393b80 > R13: 1ffffd4000072770 R14: 1ffff92000649ea8 R15: dffffc0000000000 > FS: 0000000000000000(0000) GS:ffff88818d949000(0000) knlGS:0000000000000000 > CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 > CR2: 00007fb77b215440 CR3: 000000000e946000 CR4: 00000000000006f0 > Call Trace: > <TASK> > __zap_vma_range+0x20f5/0x4f70 > unmap_vmas+0x390/0x550 > exit_mmap+0x293/0x9f0 > __mmput+0x118/0x420 > exit_mm+0x221/0x2d0 > do_exit+0x6cd/0x2360 > do_group_exit+0x22d/0x2f0 > __x64_sys_exit_group+0x3f/0x40 > x64_sys_call+0x221a/0x2240 > do_syscall_64+0x174/0x580 > entry_SYSCALL_64_after_hwframe+0x77/0x7f > RIP: 0033:0x7fb77b2d3a90 > Code: Unable to access opcode bytes at 0x7fb77b2d3a66. > RSP: 002b:00007ffe32d58618 EFLAGS: 00000246 ORIG_RAX: 00000000000000e7 > RAX: ffffffffffffffda RBX: 00007fb77b3c4860 RCX: 00007fb77b2d3a90 > RDX: 00000000000000e7 RSI: 000000000000003c RDI: 0000000000000000 > RBP: 00007fb77b3c4860 R08: 00007ffe32d58490 R09: 00007ffe32d58570 > R10: 00007ffe32d584d0 R11: 0000000000000246 R12: 0000000000000000 > R13: 0000000000000000 R14: 00007fb77b3c8658 R15: 0000000000000001 > </TASK> OK, so we might hit a uncharged folio in folio_mark_access, which isn't strange, right now it will just skip the gen bump and work as expected, problem is it's triggering this warning, and doing redundant work for lruvec lookup. To fix that, checking flags first then the lruvec should be good. Will do in V2. ^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2026-08-04 5:56 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <20260804-mglru-fg-v1-0-4d8dad39dad6@tencent.com>
2026-08-04 5:26 ` [syzbot ci] Re: mm/mglru: frequency guided promotion (MGLRU-FG) and flag cleanup syzbot ci
2026-08-04 5:56 ` Kairui Song
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox