[moderation] [mm?] general protection fault in lru_gen_test_recent (2)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 917167ed1211 Merge tag 'xtensa-20251010' of https://github..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=11ee5892580000
kernel config: https://syzkaller.appspot.com/x/.config?x=e7dba95d4cdd903c
dashboard link: https://syzkaller.appspot.com/bug?extid=41322d367db2233f3d90
compiler: gcc (Debian 12.2.0-14+deb12u1) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
CC: [ak...@linux-foundation.org axelra...@google.com da...@redhat.com han...@cmpxchg.org linux-...@vger.kernel.org linu...@kvack.org lorenzo...@oracle.com mho...@kernel.org shakee...@linux.dev wei...@google.com yua...@google.com zhengq...@bytedance.com]

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/0f12430a9f0a/disk-917167ed.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/f93d5f37d0d3/vmlinux-917167ed.xz
kernel image: https://storage.googleapis.com/syzbot-assets/c4d9e7e5ac6c/bzImage-917167ed.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+41322d...@syzkaller.appspotmail.com

Oops: general protection fault, probably for non-canonical address 0xdffffc00000009c0: 0000 [#1] SMP KASAN PTI
KASAN: probably user-memory-access in range [0x0000000000004e00-0x0000000000004e07]
CPU: 1 UID: 0 PID: 18907 Comm: syz.3.2769 Not tainted syzkaller #0 PREEMPT(full)
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/02/2025
RIP: 0010:mem_cgroup_lruvec include/linux/memcontrol.h:719 [inline]
RIP: 0010:lru_gen_test_recent+0xee/0x320 mm/workingset.c:275
Code: 68 34 b7 ff 48 85 db 0f 84 79 01 00 00 e8 5a 34 b7 ff 49 8d bd 00 4e 00 00 48 b8 00 00 00 00 00 fc ff df 48 89 fa 48 c1 ea 03 <0f> b6 04 02 84 c0 74 08 3c 03 0f 8e a3 01 00 00 4d 63 b5 00 4e 00
RSP: 0018:ffffc9000ab1f840 EFLAGS: 00010206
RAX: dffffc0000000000 RBX: ffff88801c2d8000 RCX: ffffc9000d550000
RDX: 00000000000009c0 RSI: ffffffff8204a006 RDI: 0000000000004e00
RBP: ffffc9000ab1f8d8 R08: 0000000000000001 R09: 0000000000000000
R10: 0000000000000001 R11: 0000000000000000 R12: ffffc9000ab1f8f8
R13: 0000000000000000 R14: ffffc9000ab1f8c8 R15: 0000000000000000
FS: 00007fae40c206c0(0000) GS:ffff888124ae4000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000001b32313ff8 CR3: 000000005fa16000 CR4: 00000000003526f0
Call Trace:
<TASK>
lru_gen_refault mm/workingset.c:296 [inline]
workingset_refault+0x24c/0x1060 mm/workingset.c:546
filemap_add_folio+0x23d/0x610 mm/filemap.c:993
do_read_cache_folio+0x239/0x5c0 mm/filemap.c:3991
freader_get_folio+0x337/0x930 lib/buildid.c:77
freader_fetch+0xc2/0x5e0 lib/buildid.c:120
__build_id_parse.isra.0+0xec/0x7a0 lib/buildid.c:305
do_procmap_query+0xb0e/0x1080 fs/proc/task_mmu.c:733
procfs_procmap_ioctl+0x9d/0xe0 fs/proc/task_mmu.c:813
vfs_ioctl fs/ioctl.c:51 [inline]
__do_sys_ioctl fs/ioctl.c:597 [inline]
__se_sys_ioctl fs/ioctl.c:583 [inline]
__x64_sys_ioctl+0x18b/0x210 fs/ioctl.c:583
do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
do_syscall_64+0xcd/0xfa0 arch/x86/entry/syscall_64.c:94
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7fae3fd8eec9
Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 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 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fae40c20038 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007fae3ffe6360 RCX: 00007fae3fd8eec9
RDX: 0000200000000080 RSI: 00000000c0686611 RDI: 0000000000000003
RBP: 00007fae3fe11f91 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fae3ffe63f8 R14: 00007fae3ffe6360 R15: 00007fff5f561318
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:mem_cgroup_lruvec include/linux/memcontrol.h:719 [inline]
RIP: 0010:lru_gen_test_recent+0xee/0x320 mm/workingset.c:275
Code: 68 34 b7 ff 48 85 db 0f 84 79 01 00 00 e8 5a 34 b7 ff 49 8d bd 00 4e 00 00 48 b8 00 00 00 00 00 fc ff df 48 89 fa 48 c1 ea 03 <0f> b6 04 02 84 c0 74 08 3c 03 0f 8e a3 01 00 00 4d 63 b5 00 4e 00
RSP: 0018:ffffc9000ab1f840 EFLAGS: 00010206
RAX: dffffc0000000000 RBX: ffff88801c2d8000 RCX: ffffc9000d550000
RDX: 00000000000009c0 RSI: ffffffff8204a006 RDI: 0000000000004e00
RBP: ffffc9000ab1f8d8 R08: 0000000000000001 R09: 0000000000000000
R10: 0000000000000001 R11: 0000000000000000 R12: ffffc9000ab1f8f8
R13: 0000000000000000 R14: ffffc9000ab1f8c8 R15: 0000000000000000
FS: 00007fae40c206c0(0000) GS:ffff8881249e4000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fc452c47d58 CR3: 000000005fa16000 CR4: 00000000003526f0
----------------
Code disassembly (best guess):
0: 68 34 b7 ff 48 push $0x48ffb734
5: 85 db test %ebx,%ebx
7: 0f 84 79 01 00 00 je 0x186
d: e8 5a 34 b7 ff call 0xffb7346c
12: 49 8d bd 00 4e 00 00 lea 0x4e00(%r13),%rdi
19: 48 b8 00 00 00 00 00 movabs $0xdffffc0000000000,%rax
20: fc ff df
23: 48 89 fa mov %rdi,%rdx
26: 48 c1 ea 03 shr $0x3,%rdx
* 2a: 0f b6 04 02 movzbl (%rdx,%rax,1),%eax <-- trapping instruction
2e: 84 c0 test %al,%al
30: 74 08 je 0x3a
32: 3c 03 cmp $0x3,%al
34: 0f 8e a3 01 00 00 jle 0x1dd
3a: 4d rex.WRB
3b: 63 .byte 0x63
3c: b5 00 mov $0x0,%ch
3e: 4e rex.WRX


---
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 syzk...@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