From: syzbot <syzbot+8715dd783e9b0bef43b1@syzkaller.appspotmail.com>
To: bp@alien8.de, brauner@kernel.org, dave.hansen@linux.intel.com,
hpa@zytor.com, jack@suse.cz, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, luto@kernel.org, mingo@redhat.com,
peterz@infradead.org, syzkaller-bugs@googlegroups.com,
tglx@linutronix.de, viro@zeniv.linux.org.uk, x86@kernel.org
Subject: Re: [syzbot] [fs?] kernel BUG in qlist_free_all (2)
Date: Thu, 02 Oct 2025 12:42:27 -0700 [thread overview]
Message-ID: <68ded5a3.050a0220.1696c6.0036.GAE@google.com> (raw)
In-Reply-To: <68c6c3b1.050a0220.2ff435.0382.GAE@google.com>
syzbot has found a reproducer for the following issue on:
HEAD commit: 7f7072574127 Merge tag 'kbuild-6.18-1' of git://git.kernel..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1234b092580000
kernel config: https://syzkaller.appspot.com/x/.config?x=b78ebc06b51acd7e
dashboard link: https://syzkaller.appspot.com/bug?extid=8715dd783e9b0bef43b1
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11bc1092580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=176bfd04580000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/70468cf24114/disk-7f707257.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/8126ac85fc8f/vmlinux-7f707257.xz
kernel image: https://storage.googleapis.com/syzbot-assets/0b72e383dd9d/bzImage-7f707257.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+8715dd783e9b0bef43b1@syzkaller.appspotmail.com
------------[ cut here ]------------
kernel BUG at arch/x86/mm/physaddr.c:28!
Oops: invalid opcode: 0000 [#1] SMP KASAN PTI
CPU: 1 UID: 0 PID: 5927 Comm: syz-executor Not tainted syzkaller #0 PREEMPT_{RT,(full)}
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/18/2025
RIP: 0010:__phys_addr+0x173/0x180 arch/x86/mm/physaddr.c:28
Code: e8 72 22 49 00 48 c7 c7 90 ce 21 8d 48 89 de 4c 89 f2 e8 b0 03 39 03 e9 4d ff ff ff e8 56 22 49 00 90 0f 0b e8 4e 22 49 00 90 <0f> 0b e8 46 22 49 00 90 0f 0b 0f 1f 00 90 90 90 90 90 90 90 90 90
RSP: 0018:ffffc90003fbfcd8 EFLAGS: 00010293
RAX: ffffffff81740d22 RBX: 0000607fffd49468 RCX: ffff8880256c1e00
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: ffffe8ffffd49468 R08: 0000000000000000 R09: 0000000000000000
R10: dffffc0000000000 R11: fffffbfff1d6b7e7 R12: ffffea0000000000
R13: 0000000000000000 R14: 000000000000002e R15: 0000000000000001
FS: 000055558ba17500(0000) GS:ffff888127122000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007ffc7f61af40 CR3: 00000000350ca000 CR4: 00000000003526f0
Call Trace:
<TASK>
virt_to_folio include/linux/mm.h:1180 [inline]
virt_to_slab mm/slab.h:187 [inline]
qlink_to_cache mm/kasan/quarantine.c:131 [inline]
qlist_free_all+0x39/0x140 mm/kasan/quarantine.c:176
kasan_quarantine_reduce+0x148/0x160 mm/kasan/quarantine.c:286
__kasan_slab_alloc+0x22/0x80 mm/kasan/common.c:340
kasan_slab_alloc include/linux/kasan.h:250 [inline]
slab_post_alloc_hook mm/slub.c:4191 [inline]
slab_alloc_node mm/slub.c:4240 [inline]
kmem_cache_alloc_noprof+0x114/0x2d0 mm/slub.c:4247
getname_flags+0xb8/0x540 fs/namei.c:146
user_path_at+0x24/0x60 fs/namei.c:3214
ksys_umount fs/namespace.c:2055 [inline]
__do_sys_umount fs/namespace.c:2063 [inline]
__se_sys_umount fs/namespace.c:2061 [inline]
__x64_sys_umount+0xee/0x160 fs/namespace.c:2061
do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
do_syscall_64+0xfa/0x3b0 arch/x86/entry/syscall_64.c:94
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f62cb4c01f7
Code: a8 ff ff ff f7 d8 64 89 01 48 83 c8 ff c3 0f 1f 44 00 00 31 f6 e9 09 00 00 00 66 0f 1f 84 00 00 00 00 00 b8 a6 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 01 c3 48 c7 c2 a8 ff ff ff f7 d8 64 89 02 b8
RSP: 002b:00007ffc7f61a098 EFLAGS: 00000246 ORIG_RAX: 00000000000000a6
RAX: ffffffffffffffda RBX: 00007f62cb541d7d RCX: 00007f62cb4c01f7
RDX: 0000000000000000 RSI: 0000000000000009 RDI: 00007ffc7f61b1e0
RBP: 00007ffc7f61b1cc R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00007ffc7f61b1e0
R13: 00007f62cb541d7d R14: 0000000000022677 R15: 00007ffc7f61b220
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:__phys_addr+0x173/0x180 arch/x86/mm/physaddr.c:28
Code: e8 72 22 49 00 48 c7 c7 90 ce 21 8d 48 89 de 4c 89 f2 e8 b0 03 39 03 e9 4d ff ff ff e8 56 22 49 00 90 0f 0b e8 4e 22 49 00 90 <0f> 0b e8 46 22 49 00 90 0f 0b 0f 1f 00 90 90 90 90 90 90 90 90 90
RSP: 0018:ffffc90003fbfcd8 EFLAGS: 00010293
RAX: ffffffff81740d22 RBX: 0000607fffd49468 RCX: ffff8880256c1e00
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: ffffe8ffffd49468 R08: 0000000000000000 R09: 0000000000000000
R10: dffffc0000000000 R11: fffffbfff1d6b7e7 R12: ffffea0000000000
R13: 0000000000000000 R14: 000000000000002e R15: 0000000000000001
FS: 000055558ba17500(0000) GS:ffff888127122000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007ffc7f61af40 CR3: 00000000350ca000 CR4: 00000000003526f0
---
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.
next prev parent reply other threads:[~2025-10-02 19:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-14 13:31 [syzbot] [kernel?] " syzbot
2025-10-02 19:42 ` syzbot [this message]
2025-10-04 1:04 ` [syzbot] [fs?] " syzbot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=68ded5a3.050a0220.1696c6.0036.GAE@google.com \
--to=syzbot+8715dd783e9b0bef43b1@syzkaller.appspotmail.com \
--cc=bp@alien8.de \
--cc=brauner@kernel.org \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
--cc=viro@zeniv.linux.org.uk \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®