[moderation] [fs?] kernel BUG in qlist_free_all (4)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: a989fde763f4 Merge tag 'libnvdimm-fixes-7.0-rc5' of git://..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=10b54ada580000
kernel config: https://syzkaller.appspot.com/x/.config?x=64e78d99d9bf8b4c
dashboard link: https://syzkaller.appspot.com/bug?extid=55ef36bbdcda65608180
compiler: gcc (Debian 14.2.0-19) 14.2.0, GNU ld (GNU Binutils for Debian) 2.44
CC: [bra...@kernel.org ja...@suse.cz linux-...@vger.kernel.org linux-...@vger.kernel.org vi...@zeniv.linux.org.uk]

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/a45369898044/disk-a989fde7.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/bfad5dda7ee2/vmlinux-a989fde7.xz
kernel image: https://storage.googleapis.com/syzbot-assets/a2935bf3cd58/bzImage-a989fde7.xz

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

------------[ cut here ]------------
kernel BUG at arch/x86/mm/physaddr.c:28!
Oops: invalid opcode: 0000 [#1] SMP KASAN PTI
CPU: 0 UID: 0 PID: 5192 Comm: udevd Tainted: G L syzkaller #0 PREEMPT(full)
Tainted: [L]=SOFTLOCKUP
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2026
RIP: 0010:__phys_addr+0xfa/0x180 arch/x86/mm/physaddr.c:28
Code: 48 d3 e8 48 89 c3 48 89 c6 e8 72 9c 4e 00 48 85 db 75 11 e8 88 a1 4e 00 48 89 e8 5b 5d 41 5c e9 fc 24 d7 09 e8 77 a1 4e 00 90 <0f> 0b e8 6f a1 4e 00 48 c7 c0 10 10 5c 8e 48 ba 00 00 00 00 00 fc
RSP: 0018:ffffc90002f37c30 EFLAGS: 00010293
RAX: 0000000000000000 RBX: b8ffff89005f4347 RCX: ffffffff81b97663
RDX: ffff88807ec30000 RSI: ffffffff81b976e9 RDI: ffff88807ec30000
RBP: b9007708805f4347 R08: 0000000000000006 R09: b8ffff89005f4347
R10: b9007708805f4347 R11: 0000000000000000 R12: 0000000000000000
R13: 0000000000000000 R14: ffffc90002f37c80 R15: 00000000000000c0
FS: 00007f08220ae880(0000) GS:ffff88812434a000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000200000015000 CR3: 000000007ea22000 CR4: 00000000003526f0
Call Trace:
<TASK>
virt_to_slab mm/slab.h:172 [inline]
qlink_to_cache mm/kasan/quarantine.c:131 [inline]
qlist_free_all+0x5f/0xe0 mm/kasan/quarantine.c:176
kasan_quarantine_reduce+0x1a0/0x1f0 mm/kasan/quarantine.c:286
__kasan_slab_alloc+0x69/0x90 mm/kasan/common.c:350
kasan_slab_alloc include/linux/kasan.h:253 [inline]
slab_post_alloc_hook mm/slub.c:4538 [inline]
slab_alloc_node mm/slub.c:4866 [inline]
kmem_cache_alloc_noprof+0x241/0x6e0 mm/slub.c:4873
alloc_filename fs/namei.c:142 [inline]
do_getname+0x35/0x390 fs/namei.c:182
getname include/linux/fs.h:2512 [inline]
class_filename_constructor include/linux/fs.h:2539 [inline]
do_sys_openat2+0xc5/0x1e0 fs/open.c:1365
do_sys_open fs/open.c:1372 [inline]
__do_sys_openat fs/open.c:1388 [inline]
__se_sys_openat fs/open.c:1383 [inline]
__x64_sys_openat+0x12d/0x210 fs/open.c:1383
do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
do_syscall_64+0x106/0xf80 arch/x86/entry/syscall_64.c:94
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f08218a7407
Code: 48 89 fa 4c 89 df e8 38 aa 00 00 8b 93 08 03 00 00 59 5e 48 83 f8 fc 74 1a 5b c3 0f 1f 84 00 00 00 00 00 48 8b 44 24 10 0f 05 <5b> c3 0f 1f 80 00 00 00 00 83 e2 39 83 fa 08 75 de e8 23 ff ff ff
RSP: 002b:00007fffb9e21db0 EFLAGS: 00000202 ORIG_RAX: 0000000000000101
RAX: ffffffffffffffda RBX: 00007f08220ae880 RCX: 00007f08218a7407
RDX: 0000000000080141 RSI: 000055d82b95802e RDI: ffffffffffffff9c
RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000
R10: 00000000000001a4 R11: 0000000000000202 R12: 00000000ffffffff
R13: 00000000ffffffff R14: ffffffffffffffff R15: 0000000000000000
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:__phys_addr+0xfa/0x180 arch/x86/mm/physaddr.c:28
Code: 48 d3 e8 48 89 c3 48 89 c6 e8 72 9c 4e 00 48 85 db 75 11 e8 88 a1 4e 00 48 89 e8 5b 5d 41 5c e9 fc 24 d7 09 e8 77 a1 4e 00 90 <0f> 0b e8 6f a1 4e 00 48 c7 c0 10 10 5c 8e 48 ba 00 00 00 00 00 fc
RSP: 0018:ffffc90002f37c30 EFLAGS: 00010293
RAX: 0000000000000000 RBX: b8ffff89005f4347 RCX: ffffffff81b97663
RDX: ffff88807ec30000 RSI: ffffffff81b976e9 RDI: ffff88807ec30000
RBP: b9007708805f4347 R08: 0000000000000006 R09: b8ffff89005f4347
R10: b9007708805f4347 R11: 0000000000000000 R12: 0000000000000000
R13: 0000000000000000 R14: ffffc90002f37c80 R15: 00000000000000c0
FS: 00007f08220ae880(0000) GS:ffff88812434a000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000200000015000 CR3: 000000007ea22000 CR4: 00000000003526f0


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