[v5.15] kernel BUG in balance_leaf

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 3a5928702e71 Linux 5.15.167
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=11190327980000
kernel config: https://syzkaller.appspot.com/x/.config?x=171882977b524c53
dashboard link: https://syzkaller.appspot.com/bug?extid=0ebf5974ec8b48d851e2
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/22ee27cb312d/disk-3a592870.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/90bf6a3e3d20/vmlinux-3a592870.xz
kernel image: https://storage.googleapis.com/syzbot-assets/096dd2c73ac3/Image-3a592870.gz.xz

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

------------[ cut here ]------------
kernel BUG at fs/reiserfs/prints.c:390!
Internal error: Oops - BUG: 00000000f2000800 [#1] PREEMPT SMP
Modules linked in:
CPU: 0 PID: 4297 Comm: syz.0.38 Not tainted 5.15.167-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/06/2024
pstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : __reiserfs_panic+0x150/0x154 fs/reiserfs/prints.c:384
lr : __reiserfs_panic+0x150/0x154 fs/reiserfs/prints.c:384
sp : ffff800020885a60
x29: ffff800020885b20 x28: ffff8000208863b8 x27: 0000000000000070
x26: dfff800000000000 x25: 0000000000000000 x24: ffff800020885ae0
x23: ffff800020885aa0 x22: ffff800011d04d00 x21: ffff0000e6110000
x20: ffff800011d04ce0 x19: ffff8000141ef6f7 x18: 1fffe00036831b8e
x17: 1fffe00036831b8e x16: ffff800011ac23e0 x15: ffff800014b5ef40
x14: 1ffff0000295806a x13: dfff800000000000 x12: 0000000000040000
x11: 000000000002a2f1 x10: ffff80002185e000 x9 : da13887a9dd22e00
x8 : da13887a9dd22e00 x7 : 0000000000000000 x6 : 0000000000000000
x5 : 0000000000000080 x4 : 0000000000000000 x3 : ffff80000a987d1c
x2 : ffff0001b418dd10 x1 : 0000000100000000 x0 : 0000000000000049
Call trace:
__reiserfs_panic+0x150/0x154 fs/reiserfs/prints.c:384
balance_leaf+0xd1cc/0xe860 fs/reiserfs/do_balan.c:1439
do_balance+0x27c/0x790 fs/reiserfs/do_balan.c:1888
reiserfs_paste_into_item+0x630/0x744 fs/reiserfs/stree.c:2159
reiserfs_get_block+0x1820/0x3fd0 fs/reiserfs/inode.c:1077
__block_write_begin_int+0x3ec/0x1608 fs/buffer.c:2012
__block_write_begin+0x40/0x54 fs/buffer.c:2062
reiserfs_write_begin+0x3c8/0x654 fs/reiserfs/inode.c:2790
generic_perform_write+0x24c/0x520 mm/filemap.c:3785
__generic_file_write_iter+0x230/0x454 mm/filemap.c:3912
generic_file_write_iter+0xb4/0x1b8 mm/filemap.c:3944
do_iter_readv_writev+0x420/0x5f8
do_iter_write+0x1b8/0x66c fs/read_write.c:855
vfs_iter_write+0x88/0xac fs/read_write.c:896
iter_file_splice_write+0x618/0xc48 fs/splice.c:689
do_splice_from fs/splice.c:767 [inline]
direct_splice_actor+0xe4/0x1c0 fs/splice.c:936
splice_direct_to_actor+0x408/0x9a0 fs/splice.c:891
do_splice_direct+0x1f4/0x334 fs/splice.c:979
generic_copy_file_range fs/read_write.c:1385 [inline]
vfs_copy_file_range+0x940/0x1138 fs/read_write.c:1531
__do_sys_copy_file_range fs/read_write.c:1588 [inline]
__se_sys_copy_file_range fs/read_write.c:1551 [inline]
__arm64_sys_copy_file_range+0x5f8/0x9d8 fs/read_write.c:1551
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x58/0x14c arch/arm64/kernel/syscall.c:181
el0_svc+0x7c/0x1f0 arch/arm64/kernel/entry-common.c:608
el0t_64_sync_handler+0x84/0xe4 arch/arm64/kernel/entry-common.c:626
el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584
Code: d0095be5 912800a5 aa1303e4 95c977a3 (d4210000)
---[ end trace f74bdd44a2bc8184 ]---


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

Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.