[v6.1] kernel BUG in reiserfs_update_sd_size

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: ca87e77a2ef8 Linux 6.1.34
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=111a4737280000
kernel config: https://syzkaller.appspot.com/x/.config?x=143044f84cdceac2
dashboard link: https://syzkaller.appspot.com/bug?extid=355f69812c866c9c66f8
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
userspace arch: arm64

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/1141c37ce351/disk-ca87e77a.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/de1fca0d0bb4/vmlinux-ca87e77a.xz
kernel image: https://storage.googleapis.com/syzbot-assets/c3417b70e0bf/Image-ca87e77a.gz.xz

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

REISERFS panic (device loop0): vs-13065 update_stat_data: key [1 2 0x0 SD], found item *3.5*[1 2 0(0) DIR], item_len 80, item_location 3972, free_space(entry_count) 3
------------[ cut here ]------------
kernel BUG at fs/reiserfs/prints.c:390!
Internal error: Oops - BUG: 00000000f2000800 [#1] PREEMPT SMP
Modules linked in:
CPU: 1 PID: 16092 Comm: syz-executor.0 Not tainted 6.1.34-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/25/2023
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 : ffff800022867260
x29: ffff800022867320 x28: dfff800000000000 x27: ffff00013f133000
x26: ffff800022867428 x25: ffff00013f133000 x24: ffff8000228672e0
x23: ffff8000228672a0 x22: ffff80001235d200 x21: ffff000127740000
x20: ffff80001235d1e0 x19: ffff800014cf84d7 x18: ffff800022866b60
x17: 0000000000000000 x16: ffff8000121062b4 x15: 0000000000000000
x14: 1ffff00002ab80b0 x13: dfff800000000000 x12: 0000000000040000
x11: 000000000003ffff x10: ffff800025719000 x9 : cafbe9904d3cbb00
x8 : cafbe9904d3cbb00 x7 : ffff8000082607e4 x6 : 0000000000000000
x5 : 0000000000000080 x4 : 0000000000000001 x3 : ffff80000aa75d0c
x2 : ffff0001b45cfcd0 x1 : 0000000100000000 x0 : 00000000000000a6
Call trace:
__reiserfs_panic+0x150/0x154 fs/reiserfs/prints.c:384
update_stat_data fs/reiserfs/inode.c:1424 [inline]
reiserfs_update_sd_size+0xd00/0xdb8 fs/reiserfs/inode.c:1497
reiserfs_update_sd fs/reiserfs/reiserfs.h:3099 [inline]
reiserfs_mkdir+0x60c/0x77c fs/reiserfs/namei.c:877
xattr_mkdir fs/reiserfs/xattr.c:76 [inline]
create_privroot fs/reiserfs/xattr.c:882 [inline]
reiserfs_xattr_init+0x2b0/0x6bc fs/reiserfs/xattr.c:1005
reiserfs_fill_super+0x1bfc/0x2028 fs/reiserfs/super.c:2175
mount_bdev+0x274/0x370 fs/super.c:1423
get_super_block+0x44/0x58 fs/reiserfs/super.c:2601
legacy_get_tree+0xd4/0x16c fs/fs_context.c:610
vfs_get_tree+0x90/0x274 fs/super.c:1553
do_new_mount+0x25c/0x8c4 fs/namespace.c:3040
path_mount+0x590/0xe58 fs/namespace.c:3370
do_mount fs/namespace.c:3383 [inline]
__do_sys_mount fs/namespace.c:3591 [inline]
__se_sys_mount fs/namespace.c:3568 [inline]
__arm64_sys_mount+0x45c/0x594 fs/namespace.c:3568
__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:142
do_el0_svc+0x64/0x218 arch/arm64/kernel/syscall.c:206
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:581
Code: f0084fa5 912200a5 aa1303e4 95c67e25 (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 bug is already fixed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want to change bug's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the bug is a duplicate of another bug, 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: ca87e77a2ef8 Linux 6.1.34
git tree: linux-6.1.y

console output: https://syzkaller.appspot.com/x/log.txt?x=14be725b280000

kernel config: https://syzkaller.appspot.com/x/.config?x=143044f84cdceac2
dashboard link: https://syzkaller.appspot.com/bug?extid=355f69812c866c9c66f8
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
userspace arch: arm64

syz repro: https://syzkaller.appspot.com/x/repro.syz?x=118a07c3280000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=17fd10f3280000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/1141c37ce351/disk-ca87e77a.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/de1fca0d0bb4/vmlinux-ca87e77a.xz
kernel image: https://storage.googleapis.com/syzbot-assets/c3417b70e0bf/Image-ca87e77a.gz.xz

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

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

REISERFS (device loop0): Using r5 hash to sort names

REISERFS panic (device loop0): vs-13065 update_stat_data: key [1 2 0x0 SD], found item *3.5*[1 2 0(0) DIR], item_len 80, item_location 3972, free_space(entry_count) 3
------------[ cut here ]------------
kernel BUG at fs/reiserfs/prints.c:390!
Internal error: Oops - BUG: 00000000f2000800 [#1] PREEMPT SMP
Modules linked in:

CPU: 0 PID: 4216 Comm: syz-executor190 Not tainted 6.1.34-syzkaller #0

Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/25/2023
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 : ffff80001da47260
x29: ffff80001da47320 x28: dfff800000000000 x27: ffff0000e283d2b8
x26: ffff80001da47428 x25: ffff0000e283d2b8 x24: ffff80001da472e0
x23: ffff80001da472a0 x22: ffff80001235d200 x21: ffff0000d9d2c000
x20: ffff80001235d1e0 x19: ffff800014cf84d7 x18: ffff80001da467c0

x17: 0000000000000000 x16: ffff8000121062b4 x15: 0000000000000000

x14: 0000000000000000 x13: 0000000000000001 x12: 0000000000000001
x11: ff80800008345658 x10: 0000000000000000 x9 : c42a8923db132d00
x8 : c42a8923db132d00 x7 : 0000000000000001 x6 : 0000000000000001
x5 : ffff80001da46b78 x4 : ffff8000156a2a40 x3 : ffff8000085879f4
x2 : 0000000000000001 x1 : 0000000100000000 x0 : 00000000000000a6

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.