[v6.1] kernel BUG in ocfs2_write_block

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 7ec6f9fa3d97 Linux 6.1.114
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=10f69a87980000
kernel config: https://syzkaller.appspot.com/x/.config?x=344cdb747ab79921
dashboard link: https://syzkaller.appspot.com/bug?extid=609ea64bc76a4623cbda
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/e7551ab2b38b/disk-7ec6f9fa.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/99ca69a69b01/vmlinux-7ec6f9fa.xz
kernel image: https://storage.googleapis.com/syzbot-assets/0d62742f11c2/Image-7ec6f9fa.gz.xz

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

loop5: detected capacity change from 0 to 32768
------------[ cut here ]------------
kernel BUG at fs/ocfs2/buffer_head_io.c:45!
Internal error: Oops - BUG: 00000000f2000800 [#1] PREEMPT SMP
Modules linked in:
CPU: 0 PID: 8071 Comm: syz.5.605 Not tainted 6.1.114-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024
pstate: 80400005 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : ocfs2_write_block+0x66c/0x7bc fs/ocfs2/buffer_head_io.c:45
lr : ocfs2_write_block+0x66c/0x7bc fs/ocfs2/buffer_head_io.c:45
sp : ffff800025896a20
x29: ffff800025896ac0 x28: 1fffe00018c98525 x27: ffff800025896a40
x26: dfff800000000000 x25: ffff700004b12d48 x24: ffff8000159cd360
x23: 0000000000000001 x22: 0000000000000000 x21: ffff0000dba1c000
x20: ffff0000c64c2910 x19: ffff0000e169ebf0 x18: 1fffe0003679f176
x17: ffff8000159cd000 x16: ffff800012290d3c x15: 0000000000000002
x14: 1ffff00002b3a0b0 x13: dfff800000000000 x12: 0000000000040000
x11: 000000000001e316 x10: ffff80002ff80000 x9 : ffff800009e80888
x8 : 000000000001e317 x7 : ffff800009f5610c x6 : 0000000000000000
x5 : 0000000000000000 x4 : 0000000000000001 x3 : ffff80000831e9a4
x2 : ffff0000e169ebf0 x1 : 0000000000000000 x0 : 0000000000000002
Call trace:
ocfs2_write_block+0x66c/0x7bc fs/ocfs2/buffer_head_io.c:45
ocfs2_update_disk_slot+0x3e8/0x5ec fs/ocfs2/slot_map.c:197
ocfs2_find_slot+0x490/0xac0 fs/ocfs2/slot_map.c:482
ocfs2_mount_volume+0x170/0x1508 fs/ocfs2/super.c:1806
ocfs2_fill_super+0x3adc/0x4a0c fs/ocfs2/super.c:1082
mount_bdev+0x274/0x370 fs/super.c:1443
ocfs2_mount+0x44/0x58 fs/ocfs2/super.c:1186
legacy_get_tree+0xd4/0x16c fs/fs_context.c:632
vfs_get_tree+0x90/0x274 fs/super.c:1573
do_new_mount+0x278/0x8fc fs/namespace.c:3056
path_mount+0x590/0xe5c fs/namespace.c:3386
do_mount fs/namespace.c:3399 [inline]
__do_sys_mount fs/namespace.c:3607 [inline]
__se_sys_mount fs/namespace.c:3584 [inline]
__arm64_sys_mount+0x45c/0x594 fs/namespace.c:3584
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2c0 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:140
do_el0_svc+0x64/0x218 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: b40005f7 9799dbf7 17fffe95 9799dbf5 (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: 7ec6f9fa3d97 Linux 6.1.114
git tree: linux-6.1.y

console output: https://syzkaller.appspot.com/x/log.txt?x=12ee9a87980000

kernel config: https://syzkaller.appspot.com/x/.config?x=344cdb747ab79921
dashboard link: https://syzkaller.appspot.com/bug?extid=609ea64bc76a4623cbda
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=11dbd230580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1649aca7980000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/e7551ab2b38b/disk-7ec6f9fa.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/99ca69a69b01/vmlinux-7ec6f9fa.xz
kernel image: https://storage.googleapis.com/syzbot-assets/0d62742f11c2/Image-7ec6f9fa.gz.xz

mounted in repro: https://storage.googleapis.com/syzbot-assets/c7fe5831d8ff/mount_0.gz

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

and is ignored by this kernel. Remove the mand
option from the mount to silence this warning.
=======================================================

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

CPU: 0 PID: 4291 Comm: syz-executor206 Not tainted 6.1.114-syzkaller #0

Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024
pstate: 80400005 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : ocfs2_write_block+0x66c/0x7bc fs/ocfs2/buffer_head_io.c:45
lr : ocfs2_write_block+0x66c/0x7bc fs/ocfs2/buffer_head_io.c:45

sp : ffff800020f36a20
x29: ffff800020f36ac0 x28: 1fffe0001c88dace x27: ffff800020f36a40
x26: dfff800000000000 x25: ffff7000041e6d48 x24: ffff8000159cd360
x23: 0000000000000001 x22: 0000000000000000 x21: ffff0000da144000
x20: ffff0000e446d658 x19: ffff0000e172b2f0 x18: ffff800020f36d00
x17: ffff800018aab000 x16: ffff800012290d3c x15: 0000000000000000
x14: 1ffff00002b3a0b0 x13: dfff800000000000 x12: 0000000000000001
x11: 0000000000ff0100 x10: 0000000000000000 x9 : ffff800009e80888
x8 : ffff0000dbdcd340 x7 : ffff800009f5610c x6 : 0000000000000000

x5 : 0000000000000000 x4 : 0000000000000001 x3 : ffff80000831e9a4

x2 : ffff0000e172b2f0 x1 : 0000000000000000 x0 : 0000000000000002

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.