From: syzbot <syzbot+d937c5714fc8cd6d39df@syzkaller.appspotmail.com>
To: jlbec@evilplan.org, joseph.qi@linux.alibaba.com,
linux-kernel@vger.kernel.org, mark@fasheh.com,
ocfs2-devel@lists.linux.dev, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [ocfs2?] kernel BUG in __ocfs2_claim_clusters
Date: Thu, 11 Dec 2025 21:38:24 -0800 [thread overview]
Message-ID: <693baa50.a70a0220.33cd7b.004b.GAE@google.com> (raw)
In-Reply-To: <68f777f8.050a0220.346f24.0016.GAE@google.com>
syzbot has found a reproducer for the following issue on:
HEAD commit: 05c93f3395ed Merge branch 'for-next/core' into for-kernelci
git tree: git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci
console output: https://syzkaller.appspot.com/x/log.txt?x=111f21b4580000
kernel config: https://syzkaller.appspot.com/x/.config?x=3b5338ad1e59a06c
dashboard link: https://syzkaller.appspot.com/bug?extid=d937c5714fc8cd6d39df
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
userspace arch: arm64
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11b4661a580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=102c5592580000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/6b5c913e373c/disk-05c93f33.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/15e75f1266ef/vmlinux-05c93f33.xz
kernel image: https://storage.googleapis.com/syzbot-assets/dd930129c578/Image-05c93f33.gz.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/d7f8cb828f94/mount_0.gz
fsck result: OK (log: https://syzkaller.appspot.com/x/fsck.log?x=16b4661a580000)
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+d937c5714fc8cd6d39df@syzkaller.appspotmail.com
loop0: detected capacity change from 0 to 32768
ocfs2: Mounting device (7,0) on (node local, slot 0) with writeback data mode.
------------[ cut here ]------------
kernel BUG at fs/ocfs2/suballoc.c:2390!
Internal error: Oops - BUG: 00000000f2000800 [#1] SMP
Modules linked in:
CPU: 0 UID: 0 PID: 6742 Comm: syz.0.17 Not tainted syzkaller #0 PREEMPT
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/03/2025
pstate: 83400005 (Nzcv daif +PAN -UAO +TCO +DIT -SSBS BTYPE=--)
pc : __ocfs2_claim_clusters+0x768/0x7c4 fs/ocfs2/suballoc.c:2390
lr : __ocfs2_claim_clusters+0x768/0x7c4 fs/ocfs2/suballoc.c:2390
sp : ffff8000a1706a60
x29: ffff8000a1706ba0 x28: 0000000000000040 x27: 0000000000000040
x26: dfff800000000000 x25: 1fffe00018d35af0 x24: ffff0000c69ad780
x23: 0000000000000039 x22: ffff0000da3ec000 x21: 0000000000000000
x20: ffff0000c69ad798 x19: ffff7000142e0d54 x18: 1fffe000337d4a90
x17: ffff800093335000 x16: ffff80008ad6b188 x15: 0000000000000005
x14: 1ffff000142e0d58 x13: 0000000000000000 x12: 0000000000000000
x11: ffff7000142e0d5d x10: 0000000000ff0100 x9 : 0000000000000000
x8 : ffff0000c8278000 x7 : 0000000000000000 x6 : 0000000000000000
x5 : ffff8000a1706d90 x4 : 0000000000000000 x3 : 0000000000000020
x2 : 0000000000000008 x1 : 0000000000000040 x0 : 0000000000000040
Call trace:
__ocfs2_claim_clusters+0x768/0x7c4 fs/ocfs2/suballoc.c:2390 (P)
ocfs2_claim_clusters fs/ocfs2/suballoc.c:2458 [inline]
ocfs2_block_group_claim_bits fs/ocfs2/suballoc.c:474 [inline]
ocfs2_block_group_grow_discontig fs/ocfs2/suballoc.c:515 [inline]
ocfs2_block_group_alloc_discontig fs/ocfs2/suballoc.c:641 [inline]
ocfs2_block_group_alloc fs/ocfs2/suballoc.c:703 [inline]
ocfs2_reserve_suballoc_bits+0x1b64/0x3b9c fs/ocfs2/suballoc.c:834
ocfs2_reserve_new_inode+0x3c0/0xac0 fs/ocfs2/suballoc.c:1074
ocfs2_mknod+0x710/0x1cf0 fs/ocfs2/namei.c:306
ocfs2_create+0x190/0x474 fs/ocfs2/namei.c:676
lookup_open fs/namei.c:3796 [inline]
open_last_lookups fs/namei.c:3895 [inline]
path_openat+0x12d8/0x2c40 fs/namei.c:4131
do_filp_open+0x18c/0x36c fs/namei.c:4161
do_sys_openat2+0x11c/0x1b4 fs/open.c:1437
do_sys_open fs/open.c:1452 [inline]
__do_sys_openat fs/open.c:1468 [inline]
__se_sys_openat fs/open.c:1463 [inline]
__arm64_sys_openat+0x120/0x158 fs/open.c:1463
__invoke_syscall arch/arm64/kernel/syscall.c:35 [inline]
invoke_syscall+0x98/0x254 arch/arm64/kernel/syscall.c:49
el0_svc_common+0xe8/0x23c arch/arm64/kernel/syscall.c:132
do_el0_svc+0x48/0x58 arch/arm64/kernel/syscall.c:151
el0_svc+0x5c/0x254 arch/arm64/kernel/entry-common.c:724
el0t_64_sync_handler+0x84/0x12c arch/arm64/kernel/entry-common.c:743
el0t_64_sync+0x198/0x19c arch/arm64/kernel/entry.S:596
Code: aa1803e2 94384723 17ffff3d 97951fa1 (d4210000)
---[ end trace 0000000000000000 ]---
---
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.
prev parent reply other threads:[~2025-12-12 5:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-21 12:09 syzbot
2025-12-12 5:38 ` syzbot [this message]
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=693baa50.a70a0220.33cd7b.004b.GAE@google.com \
--to=syzbot+d937c5714fc8cd6d39df@syzkaller.appspotmail.com \
--cc=jlbec@evilplan.org \
--cc=joseph.qi@linux.alibaba.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark@fasheh.com \
--cc=ocfs2-devel@lists.linux.dev \
--cc=syzkaller-bugs@googlegroups.com \
/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®