Re: [syzbot] [ocfs2?] kernel BUG in __ocfs2_move_extents_range

[syzbot <syzbot+f2107d999290b8166267@syzkaller.appspotmail.com>]

syzbot has found a reproducer for the following issue on:

HEAD commit:    8f5ae30d69d7 Linux 6.17-rc1
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=1777e3a2580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=8c5ac3d8b8abfcb
dashboard link: https://syzkaller.appspot.com/bug?extid=f2107d999290b8166267
compiler:       Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7
userspace arch: arm64
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=1599cba2580000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=1399cba2580000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/18a2e4bd0c4a/disk-8f5ae30d.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/3b5395881b25/vmlinux-8f5ae30d.xz
kernel image: https://storage.googleapis.com/syzbot-assets/e875f4e3b7ff/Image-8f5ae30d.gz.xz
mounted in repro #1: https://storage.googleapis.com/syzbot-assets/cd2aa4d483e9/mount_0.gz
  fsck result: OK (log: https://syzkaller.appspot.com/x/fsck.log?x=1199cba2580000)
mounted in repro #2: https://storage.googleapis.com/syzbot-assets/a56844890eb2/mount_5.gz
  fsck result: failed (log: https://syzkaller.appspot.com/x/fsck.log?x=1377e3a2580000)

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

=======================================================
ocfs2: Mounting device (7,0) on (node local, slot 0) with ordered data mode.
------------[ cut here ]------------
kernel BUG at fs/ocfs2/suballoc.c:1382!
Internal error: Oops - BUG: 00000000f2000800 [#1]  SMP
Modules linked in:
CPU: 0 UID: 0 PID: 6767 Comm: syz.0.17 Not tainted 6.17.0-rc1-syzkaller-g8f5ae30d69d7 #0 PREEMPT 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/30/2025
pstate: 83400005 (Nzcv daif +PAN -UAO +TCO +DIT -SSBS BTYPE=--)
pc : ocfs2_block_group_set_bits+0x780/0x8e8 fs/ocfs2/suballoc.c:1382
lr : ocfs2_block_group_set_bits+0x780/0x8e8 fs/ocfs2/suballoc.c:1382
sp : ffff8000a10b71a0
x29: ffff8000a10b7260 x28: ffff0000f456cfb8 x27: ffff0000c8f34000
x26: ffff0000f46155d8 x25: ffff0000c6265000 x24: 1ffff00014216e40
x23: ffff0000c626500c x22: dfff800000000000 x21: 0000000000000002
x20: 0000000000000004 x19: 0000000000000000 x18: 00000000ffffffff
x17: ffff800093507000 x16: ffff80008afd94bc x15: 0000000000000001
x14: 0000000000000000 x13: 00000000fffffffc x12: 0000000000000000
x11: 0000000000000000 x10: 0000000000ff0100 x9 : 0000000000000000
x8 : ffff0000d38dbd00 x7 : 0000000000000000 x6 : 0000000000000000
x5 : 0000000000000004 x4 : 0000000000000001 x3 : ffff0000def9fae0
x2 : ffff0000c6265000 x1 : 0000000000000002 x0 : 0000000000000004
Call trace:
 ocfs2_block_group_set_bits+0x780/0x8e8 fs/ocfs2/suballoc.c:1382 (P)
 ocfs2_move_extent fs/ocfs2/move_extents.c:687 [inline]
 __ocfs2_move_extents_range+0x2104/0x2ad8 fs/ocfs2/move_extents.c:859
 ocfs2_move_extents+0x314/0x7f0 fs/ocfs2/move_extents.c:926
 ocfs2_ioctl_move_extents+0x424/0x5f0 fs/ocfs2/move_extents.c:1052
 ocfs2_ioctl+0x1c4/0x738 fs/ocfs2/ioctl.c:946
 vfs_ioctl fs/ioctl.c:51 [inline]
 __do_sys_ioctl fs/ioctl.c:598 [inline]
 __se_sys_ioctl fs/ioctl.c:584 [inline]
 __arm64_sys_ioctl+0x14c/0x1c4 fs/ioctl.c:584
 __invoke_syscall arch/arm64/kernel/syscall.c:35 [inline]
 invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:49
 el0_svc_common+0x130/0x23c arch/arm64/kernel/syscall.c:132
 do_el0_svc+0x48/0x58 arch/arm64/kernel/syscall.c:151
 el0_svc+0x58/0x180 arch/arm64/kernel/entry-common.c:879
 el0t_64_sync_handler+0x84/0x12c arch/arm64/kernel/entry-common.c:898
 el0t_64_sync+0x198/0x19c arch/arm64/kernel/entry.S:596
Code: 17ffffa8 9795f801 d4210000 9795f7ff (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.