[v6.1] kernel BUG in nilfs_btnode_create_block

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: fa74641fb6b9 Linux 6.1.29
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1153cbf9280000
kernel config: https://syzkaller.appspot.com/x/.config?x=7454aa89ac475d7b
dashboard link: https://syzkaller.appspot.com/bug?extid=1bd51d7e4356491a3e0a
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=11b9d8c5280000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1556faee280000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/53e4da6b145c/disk-fa74641f.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/adeb1a2cfa86/vmlinux-fa74641f.xz
kernel image: https://storage.googleapis.com/syzbot-assets/c976f1155d08/Image-fa74641f.gz.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/b3f4d76663a9/mount_0.gz

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

------------[ cut here ]------------
kernel BUG at fs/nilfs2/btnode.c:59!
Internal error: Oops - BUG: 00000000f2000800 [#1] PREEMPT SMP
Modules linked in:
CPU: 1 PID: 4309 Comm: segctord Not tainted 6.1.29-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/28/2023
pstate: 80400005 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : nilfs_btnode_create_block+0x3b0/0x49c fs/nilfs2/btnode.c:58
lr : nilfs_btnode_create_block+0x3b0/0x49c fs/nilfs2/btnode.c:58
sp : ffff80001db67070
x29: ffff80001db67070 x28: 000000000000122f x27: ffff0000d81ee9f0
x26: ffff0000df342ae0 x25: 1fffe0001c402f22 x24: dfff800000000000
x23: 000000000000000a x22: 0000000000020011 x21: ffff0000e2a78e28
x20: 000000000000122f x19: ffff0000e2017910 x18: ffff0000e20f5350
x17: ffff80001559d000 x16: ffff800008304574 x15: 0000000000000000
x14: 0000000000000000 x13: 0000000000000406 x12: 0000000000000001
x11: ff80800008b2c21c x10: 0000000000000000 x9 : ffff800008b2c21c
x8 : 00000000ffffffff x7 : ffff800008756b20 x6 : 0000000000000000
x5 : 0000000000000000 x4 : 0000000000000000 x3 : ffff800008b2c214
x2 : 0000000000000001 x1 : 0000000000000004 x0 : 0000000000000001
Call trace:
nilfs_btnode_create_block+0x3b0/0x49c fs/nilfs2/btnode.c:58
nilfs_btnode_prepare_change_key+0x304/0x3d8 fs/nilfs2/btnode.c:219
nilfs_btree_prepare_update_v+0x2c0/0x378 fs/nilfs2/btree.c:1928
nilfs_btree_prepare_propagate_v fs/nilfs2/btree.c:1995 [inline]
nilfs_btree_propagate_v fs/nilfs2/btree.c:2040 [inline]
nilfs_btree_propagate+0x850/0xe90 fs/nilfs2/btree.c:2097
nilfs_bmap_propagate+0x7c/0x130 fs/nilfs2/bmap.c:345
nilfs_collect_file_data+0x54/0xe8 fs/nilfs2/segment.c:587
nilfs_segctor_apply_buffers+0x170/0x31c fs/nilfs2/segment.c:1037
nilfs_segctor_scan_file+0x6d4/0xd8c fs/nilfs2/segment.c:1086
nilfs_segctor_collect_blocks fs/nilfs2/segment.c:1195 [inline]
nilfs_segctor_collect fs/nilfs2/segment.c:1522 [inline]
nilfs_segctor_do_construct+0x16f8/0x640c fs/nilfs2/segment.c:2068
nilfs_segctor_construct+0x110/0x768 fs/nilfs2/segment.c:2402
nilfs_segctor_thread_construct fs/nilfs2/segment.c:2510 [inline]
nilfs_segctor_thread+0x3d4/0xd74 fs/nilfs2/segment.c:2593
kthread+0x250/0x2d8 kernel/kthread.c:376
ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:860
Code: 14000002 979dcc60 aa1303e0 9400003c (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 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.

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]

Auto-closing this bug as obsolete.
No recent activity, existing reproducers are no longer triggering the issue.