On Mon, Dec 9, 2024 at 9:14 AM syzbot <syzbot+7d6336b144d8db5ad602@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote: > > Hello, > > syzbot found the following issue on: > > HEAD commit: af2ea8ab7a54 Add linux-next specific files for 20241205 20241205 has "mm/mglru: rework workingset protection" v1 [1], and the warning was fixed in v2. [1] https://lore.kernel.org/linux-mm/20241202032823.2741019-7-yuzhao@xxxxxxxxxx/ > git tree: linux-next > console output: https://syzkaller.appspot.com/x/log.txt?x=1232c3e8580000 > kernel config: https://syzkaller.appspot.com/x/.config?x=76f158395f6f15fd > dashboard link: https://syzkaller.appspot.com/bug?extid=7d6336b144d8db5ad602 > compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40 > syz repro: https://syzkaller.appspot.com/x/repro.syz?x=179d14df980000 > C reproducer: https://syzkaller.appspot.com/x/repro.c?x=13be48f8580000 > > Downloadable assets: > disk image: https://storage.googleapis.com/syzbot-assets/8af0861258fa/disk-af2ea8ab.raw.xz > vmlinux: https://storage.googleapis.com/syzbot-assets/ffb38cf7a344/vmlinux-af2ea8ab.xz > kernel image: https://storage.googleapis.com/syzbot-assets/6fbd2e50358a/bzImage-af2ea8ab.xz > mounted in repro: https://storage.googleapis.com/syzbot-assets/c5bc8f20b5e4/mount_13.gz > > IMPORTANT: if you fix the issue, please add the following tag to the commit: > Reported-by: syzbot+7d6336b144d8db5ad602@xxxxxxxxxxxxxxxxxxxxxxxxx > > reclaim_folio_list+0x13c/0x5f0 mm/vmscan.c:2183 > reclaim_pages+0x49e/0x5e0 mm/vmscan.c:2220 > madvise_cold_or_pageout_pte_range+0x1ea8/0x2360 mm/madvise.c:558 > walk_pmd_range mm/pagewalk.c:130 [inline] > walk_pud_range mm/pagewalk.c:226 [inline] > walk_p4d_range mm/pagewalk.c:264 [inline] > walk_pgd_range+0xc3d/0x17e0 mm/pagewalk.c:305 > __walk_page_range+0x15f/0x700 mm/pagewalk.c:412 > walk_page_range_mm+0x58f/0x7c0 mm/pagewalk.c:505 > madvise_pageout_page_range mm/madvise.c:617 [inline] > madvise_pageout mm/madvise.c:644 [inline] > madvise_vma_behavior mm/madvise.c:1266 [inline] > madvise_walk_vmas mm/madvise.c:1502 [inline] > do_madvise+0x3944/0x4d90 mm/madvise.c:1689 > __do_sys_madvise mm/madvise.c:1705 [inline] > __se_sys_madvise mm/madvise.c:1703 [inline] > __x64_sys_madvise+0xa6/0xc0 mm/madvise.c:1703 > do_syscall_x64 arch/x86/entry/common.c:52 [inline] > do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83 > entry_SYSCALL_64_after_hwframe+0x77/0x7f > ------------[ cut here ]------------ > WARNING: CPU: 0 PID: 14073 at ./include/linux/mm_inline.h:265 lru_gen_add_folio+0xad2/0xc30 include/linux/mm_inline.h:265 > Modules linked in: > CPU: 0 UID: 0 PID: 14073 Comm: syz-executor858 Not tainted 6.13.0-rc1-next-20241205-syzkaller #0 > Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024 > RIP: 0010:lru_gen_add_folio+0xad2/0xc30 include/linux/mm_inline.h:265 > Code: 44 89 c2 ff ba 01 00 00 00 e9 8b fa ff ff e8 35 89 c2 ff 4c 89 ff 48 c7 c6 c0 c8 13 8c e8 c6 41 0c 00 c6 05 f1 32 27 0e 01 90 <0f> 0b 90 e9 82 f6 ff ff 89 d9 80 e1 07 38 c1 0f 8c 19 f7 ff ff 48 > RSP: 0018:ffffc9000e786ce0 EFLAGS: 00010046 > RAX: 72f3d3d7c701e600 RBX: ffffea0000cbb548 RCX: ffffc9000e786803 > RDX: 0000000000000003 RSI: ffffffff8c0aa440 RDI: ffffffff8c5fbe80 > RBP: ffffc9000e786dd8 R08: ffffffff9019d9b7 R09: 1ffffffff2033b36 > R10: dffffc0000000000 R11: fffffbfff2033b37 R12: 0000000000000000 > R13: 1ffffd40001976a8 R14: 0000020000000000 R15: ffffea0000cbb540 > FS: 00007f0542a006c0(0000) GS:ffff8880b8600000(0000) knlGS:0000000000000000 > CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 > CR2: 00007f05432da864 CR3: 000000002eb56000 CR4: 00000000003526f0 > DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 > DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 > Call Trace: > <TASK> > lruvec_add_folio include/linux/mm_inline.h:352 [inline] > lru_add+0x704/0xdb0 mm/swap.c:154 > folio_batch_move_lru+0x26b/0x420 mm/swap.c:168 > __folio_batch_add_and_move+0x5bb/0xd70 mm/swap.c:196 > filemap_add_folio+0x24e/0x380 mm/filemap.c:987 > page_cache_ra_unbounded+0x32c/0x720 mm/readahead.c:263 > do_async_mmap_readahead mm/filemap.c:3212 [inline] > filemap_fault+0x818/0x1490 mm/filemap.c:3311 > __do_fault+0x135/0x390 mm/memory.c:4978 > do_read_fault mm/memory.c:5393 [inline] > do_fault mm/memory.c:5527 [inline] > do_pte_missing mm/memory.c:4048 [inline] > handle_pte_fault+0x39eb/0x5ee0 mm/memory.c:5872 > __handle_mm_fault mm/memory.c:6015 [inline] > handle_mm_fault+0x1106/0x1bb0 mm/memory.c:6183 > faultin_page mm/gup.c:1200 [inline] > __get_user_pages+0x1b31/0x4370 mm/gup.c:1495 > populate_vma_page_range+0x264/0x330 mm/gup.c:1933 > __mm_populate+0x27a/0x460 mm/gup.c:2036 > mm_populate include/linux/mm.h:3389 [inline] > vm_mmap_pgoff+0x303/0x430 mm/util.c:585 > ksys_mmap_pgoff+0x4eb/0x720 mm/mmap.c:545 > do_syscall_x64 arch/x86/entry/common.c:52 [inline] > do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83 > entry_SYSCALL_64_after_hwframe+0x77/0x7f > RIP: 0033:0x7f0543256069 > Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 51 1f 00 00 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b0 ff ff ff f7 d8 64 89 01 48 > RSP: 002b:00007f0542a00158 EFLAGS: 00000246 ORIG_RAX: 0000000000000009 > RAX: ffffffffffffffda RBX: 00007f05432d8708 RCX: 00007f0543256069 > RDX: 0000000001000002 RSI: 0000000000b36000 RDI: 0000000020000000 > RBP: 00007f05432d8700 R08: 0000000000000005 R09: 0000000000000000 > R10: 0000000000028011 R11: 0000000000000246 R12: 00007f05432d870c > R13: 0000000000000006 R14: 00007ffce0a6ecb0 R15: 00007ffce0a6ed98 > </TASK> > > > --- > 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@xxxxxxxxxxxxxxxx. > > 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 syzbot to run the reproducer, reply with: > #syz test: git://repo/address.git branch-or-commit-hash > If you attach or paste a git patch, syzbot will apply it before testing. > > 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 >
