[syzbot] [mm?] general protection fault in workingset_refault

From: syzbot
Date: Sun Dec 22 2024 - 05:44:35 EST

Hello,

syzbot found the following issue on:

HEAD commit: 8faabc041a00 Merge tag 'net-6.13-rc4' of git://git.kernel...
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=10f39cf8580000
kernel config: https://syzkaller.appspot.com/x/.config?x=c22efbd20f8da769
dashboard link: https://syzkaller.appspot.com/bug?extid=d21d8cd32443d6fbded1
compiler: gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/0bdb6cecaf61/disk-8faabc04.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/98b22dfadac0/vmlinux-8faabc04.xz
kernel image: https://storage.googleapis.com/syzbot-assets/65a511d3ba7f/bzImage-8faabc04.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+d21d8cd32443d6fbded1@xxxxxxxxxxxxxxxxxxxxxxxxx

Oops: general protection fault, probably for non-canonical address 0xdffffc0000000998: 0000 [#1] PREEMPT SMP KASAN PTI
KASAN: probably user-memory-access in range [0x0000000000004cc0-0x0000000000004cc7]
CPU: 1 UID: 0 PID: 6298 Comm: syz.0.89 Not tainted 6.13.0-rc3-syzkaller-00136-g8faabc041a00 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/25/2024
RIP: 0010:mem_cgroup_lruvec include/linux/memcontrol.h:707 [inline]
RIP: 0010:lru_gen_test_recent mm/workingset.c:274 [inline]
RIP: 0010:lru_gen_refault mm/workingset.c:293 [inline]
RIP: 0010:workingset_refault+0x234/0x1390 mm/workingset.c:548
Code: d2 6f b9 ff 4d 85 f6 0f 84 80 07 00 00 e8 c4 6f b9 ff 49 8d bf c0 4c 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 ac 0d 00 00 49 63 87 c0 4c 00
RSP: 0018:ffffc9000b1e78f0 EFLAGS: 00010202
RAX: dffffc0000000000 RBX: ffffea000153d240 RCX: ffffc9000b429000
RDX: 0000000000000998 RSI: ffffffff81dfdf2c RDI: 0000000000004cc0
RBP: 1ffff9200163cf24 R08: 0000000000000000 R09: fffffbfff2039c42
R10: ffffffff901ce217 R11: 0000000000000003 R12: 00fff00000000001
R13: 0000000000000dff R14: ffff888140adc000 R15: 0000000000000000
FS: 00007efe392656c0(0000) GS:ffff8880b8700000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000000000 CR3: 00000000788be000 CR4: 00000000003526f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
filemap_add_folio+0x1b0/0x220 mm/filemap.c:986
do_read_cache_folio+0x239/0x5c0 mm/filemap.c:3793
freader_get_folio+0x337/0x8e0 lib/buildid.c:77
freader_fetch+0xc2/0x5b0 lib/buildid.c:120
__build_id_parse.isra.0+0xef/0x770 lib/buildid.c:305
do_procmap_query+0xdb2/0xfe0 fs/proc/task_mmu.c:534
procfs_procmap_ioctl+0x7d/0xb0 fs/proc/task_mmu.c:613
vfs_ioctl fs/ioctl.c:51 [inline]
__do_sys_ioctl fs/ioctl.c:906 [inline]
__se_sys_ioctl fs/ioctl.c:892 [inline]
__x64_sys_ioctl+0x190/0x200 fs/ioctl.c:892
do_syscall_x64 arch/x86/entry/common.c:52 [inline]
do_syscall_64+0xcd/0x250 arch/x86/entry/common.c:83
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7efe38385d29
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:00007efe39265038 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007efe38575fa0 RCX: 00007efe38385d29
RDX: 0000000020000180 RSI: 00000000c0686611 RDI: 0000000000000003
RBP: 00007efe38401aa8 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000000 R14: 00007efe38575fa0 R15: 00007ffc63357c18
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:mem_cgroup_lruvec include/linux/memcontrol.h:707 [inline]
RIP: 0010:lru_gen_test_recent mm/workingset.c:274 [inline]
RIP: 0010:lru_gen_refault mm/workingset.c:293 [inline]
RIP: 0010:workingset_refault+0x234/0x1390 mm/workingset.c:548
Code: d2 6f b9 ff 4d 85 f6 0f 84 80 07 00 00 e8 c4 6f b9 ff 49 8d bf c0 4c 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 ac 0d 00 00 49 63 87 c0 4c 00
RSP: 0018:ffffc9000b1e78f0 EFLAGS: 00010202
RAX: dffffc0000000000 RBX: ffffea000153d240 RCX: ffffc9000b429000
RDX: 0000000000000998 RSI: ffffffff81dfdf2c RDI: 0000000000004cc0
RBP: 1ffff9200163cf24 R08: 0000000000000000 R09: fffffbfff2039c42
R10: ffffffff901ce217 R11: 0000000000000003 R12: 00fff00000000001
R13: 0000000000000dff R14: ffff888140adc000 R15: 0000000000000000
FS: 00007efe392656c0(0000) GS:ffff8880b8700000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000000110c3073d1 CR3: 00000000788be000 CR4: 00000000003526f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
----------------
Code disassembly (best guess), 1 bytes skipped:
0: 6f outsl %ds:(%rsi),(%dx)
1: b9 ff 4d 85 f6 mov $0xf6854dff,%ecx
6: 0f 84 80 07 00 00 je 0x78c
c: e8 c4 6f b9 ff call 0xffb96fd5
11: 49 8d bf c0 4c 00 00 lea 0x4cc0(%r15),%rdi
18: 48 b8 00 00 00 00 00 movabs $0xdffffc0000000000,%rax
1f: fc ff df
22: 48 89 fa mov %rdi,%rdx
25: 48 c1 ea 03 shr $0x3,%rdx
* 29: 0f b6 04 02 movzbl (%rdx,%rax,1),%eax <-- trapping instruction
2d: 84 c0 test %al,%al
2f: 74 08 je 0x39
31: 3c 03 cmp $0x3,%al
33: 0f 8e ac 0d 00 00 jle 0xde5
39: 49 rex.WB
3a: 63 .byte 0x63
3b: 87 c0 xchg %eax,%eax
3d: 4c rex.WR


---
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 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