[v6.1] kernel BUG in ocfs2_write_cluster_by_desc

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 344a09659766 Linux 6.1.131
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=12cecc4c580000
kernel config: https://syzkaller.appspot.com/x/.config?x=14d5dbae75afa499
dashboard link: https://syzkaller.appspot.com/bug?extid=878dcbda971e40895816
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm64

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/8c94453bbad3/disk-344a0965.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/6bf26518c790/vmlinux-344a0965.xz
kernel image: https://storage.googleapis.com/syzbot-assets/424da9a470eb/Image-344a0965.gz.xz

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

ocfs2: Mounting device (7,1) on (node local, slot 0) with ordered data mode.
------------[ cut here ]------------
kernel BUG at fs/ocfs2/aops.c:1180!
Internal error: Oops - BUG: 00000000f2000800 [#1] PREEMPT SMP
Modules linked in:
CPU: 1 PID: 5069 Comm: syz.1.103 Not tainted 6.1.131-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2025
pstate: 20400005 (nzCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : ocfs2_write_cluster fs/ocfs2/aops.c:1180 [inline]
pc : ocfs2_write_cluster_by_desc+0x1a28/0x1a54 fs/ocfs2/aops.c:1241
lr : ocfs2_write_cluster fs/ocfs2/aops.c:1180 [inline]
lr : ocfs2_write_cluster_by_desc+0x1a28/0x1a54 fs/ocfs2/aops.c:1241
sp : ffff8000228e6a80
x29: ffff8000228e6e20 x28: 0000000000001000 x27: ffff0000ce8ec028
x26: 0000000008600000 x25: ffff8000228e6c80 x24: 0000000000000000
x23: dfff800000000000 x22: ffff0000ce8ec014 x21: 0000000000002180
x20: 0000000000000000 x19: 0000000000000005 x18: 0000000000400008
x17: 0000000000080000 x16: ffff80000825bfc4 x15: ffff80002240b000
x14: 1ffff00002b600b2 x13: dfff800000000000 x12: 0000000000400008
x11: 0000000000ff0100 x10: 0000000000000003 x9 : ffff800009f04134
x8 : ffff0000ec39d340 x7 : ffff800009f4a760 x6 : 0000000000000000
x5 : 0000000000000000 x4 : 0000000000000001 x3 : ffff80000831b328
x2 : 0000000000000001 x1 : 0000000000000000 x0 : 0000000000000000
Call trace:
ocfs2_write_cluster fs/ocfs2/aops.c:1180 [inline]
ocfs2_write_cluster_by_desc+0x1a28/0x1a54 fs/ocfs2/aops.c:1241
ocfs2_write_begin_nolock+0x2cc4/0x3f6c fs/ocfs2/aops.c:1817
ocfs2_write_begin+0x1ac/0x38c fs/ocfs2/aops.c:1904
generic_perform_write+0x278/0x55c mm/filemap.c:3845
__generic_file_write_iter+0x168/0x388 mm/filemap.c:3973
ocfs2_file_write_iter+0x156c/0x1f48 fs/ocfs2/file.c:2469
call_write_iter include/linux/fs.h:2265 [inline]
new_sync_write fs/read_write.c:491 [inline]
vfs_write+0x610/0x91c fs/read_write.c:584
ksys_pwrite64 fs/read_write.c:699 [inline]
__do_sys_pwrite64 fs/read_write.c:709 [inline]
__se_sys_pwrite64 fs/read_write.c:706 [inline]
__arm64_sys_pwrite64+0x188/0x220 fs/read_write.c:706
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2bc arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:140
do_el0_svc+0x58/0x13c arch/arm64/kernel/syscall.c:204
el0_svc+0x58/0x168 arch/arm64/kernel/entry-common.c:637
el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655
el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:585
Code: 52808fe2 9406affd d4210000 9797c2b3 (d4210000)
---[ end trace 0000000000000000 ]---


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

[syzbot]

syzbot has found a reproducer for the following issue on:

HEAD commit: 344a09659766 Linux 6.1.131
git tree: linux-6.1.y

console output: https://syzkaller.appspot.com/x/log.txt?x=13834c4c580000

kernel config: https://syzkaller.appspot.com/x/.config?x=14d5dbae75afa499
dashboard link: https://syzkaller.appspot.com/bug?extid=878dcbda971e40895816
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm64

syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15c1e5e4580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=115ecc4c580000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/8c94453bbad3/disk-344a0965.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/6bf26518c790/vmlinux-344a0965.xz
kernel image: https://storage.googleapis.com/syzbot-assets/424da9a470eb/Image-344a0965.gz.xz

mounted in repro: https://storage.googleapis.com/syzbot-assets/2d9295ae0c84/mount_0.gz
fsck result: OK (log: https://syzkaller.appspot.com/x/fsck.log?x=11c1e5e4580000)

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

=======================================================
JBD2: Ignoring recovery information on journal
ocfs2: Mounting device (7,0) on (node local, slot 0) with ordered data mode.

------------[ cut here ]------------
kernel BUG at fs/ocfs2/aops.c:1180!
Internal error: Oops - BUG: 00000000f2000800 [#1] PREEMPT SMP
Modules linked in:

CPU: 1 PID: 4293 Comm: syz-executor395 Not tainted 6.1.131-syzkaller #0

Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2025

pstate: 80400005 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)

pc : ocfs2_write_cluster fs/ocfs2/aops.c:1180 [inline]
pc : ocfs2_write_cluster_by_desc+0x1a28/0x1a54 fs/ocfs2/aops.c:1241
lr : ocfs2_write_cluster fs/ocfs2/aops.c:1180 [inline]
lr : ocfs2_write_cluster_by_desc+0x1a28/0x1a54 fs/ocfs2/aops.c:1241

sp : ffff800021166a80
x29: ffff800021166e20 x28: 0000000000001000 x27: ffff0000daa8c028
x26: 0000000008600000 x25: ffff800021166c80 x24: 0000000000000000
x23: dfff800000000000 x22: ffff0000daa8c014 x21: 0000000000002180
x20: 0000000000000000 x19: 0000000000000005 x18: ffff800021165f40
x17: ffff800018c58000 x16: ffff80000825bfc4 x15: 0000000000000000
x14: 1ffff00002b600b2 x13: dfff800000000000 x12: 0000000000000001
x11: 0000000000ff0100 x10: 0000000000000000 x9 : ffff800009f04134
x8 : ffff0000d955d340 x7 : ffff800009f4a760 x6 : 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.