[v6.1] WARNING in udf_prealloc_blocks

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 909ba1f1b414 Linux 6.1.90
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=10fb4ae4980000
kernel config: https://syzkaller.appspot.com/x/.config?x=3be6d6f79b879a67
dashboard link: https://syzkaller.appspot.com/bug?extid=ac959d323f0a5fa55cc9
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/63178de7cba7/disk-909ba1f1.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/25dec90d8126/vmlinux-909ba1f1.xz
kernel image: https://storage.googleapis.com/syzbot-assets/25509ea1c6cd/bzImage-909ba1f1.xz

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

------------[ cut here ]------------
WARNING: CPU: 1 PID: 6028 at fs/udf/udfdecl.h:116 udf_add_free_space fs/udf/balloc.c:125 [inline]
WARNING: CPU: 1 PID: 6028 at fs/udf/udfdecl.h:116 udf_table_prealloc_blocks fs/udf/balloc.c:576 [inline]
WARNING: CPU: 1 PID: 6028 at fs/udf/udfdecl.h:116 udf_prealloc_blocks+0xf0b/0x1310 fs/udf/balloc.c:709
Modules linked in:
CPU: 1 PID: 6028 Comm: syz-executor.2 Not tainted 6.1.90-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/02/2024
RIP: 0010:udf_updated_lvid fs/udf/udfdecl.h:114 [inline]
RIP: 0010:udf_add_free_space fs/udf/balloc.c:125 [inline]
RIP: 0010:udf_table_prealloc_blocks fs/udf/balloc.c:576 [inline]
RIP: 0010:udf_prealloc_blocks+0xf0b/0x1310 fs/udf/balloc.c:709
Code: 48 8d 65 d8 5b 41 5c 41 5d 41 5e 41 5f 5d c3 e8 db 45 8e fe e9 4f f7 ff ff e8 d1 45 8e fe 0f 0b e9 6b f8 ff ff e8 c5 45 8e fe <0f> 0b e9 c9 fe ff ff 89 d9 80 e1 07 fe c1 38 c1 0f 8c 0c f2 ff ff
RSP: 0000:ffffc90004eb72e0 EFLAGS: 00010283
RAX: ffffffff82fc478b RBX: 00000000f93dbffe RCX: 0000000000040000
RDX: ffffc90005da4000 RSI: 0000000000015b6f RDI: 0000000000015b70
RBP: ffffc90004eb7450 R08: ffffffff82fc464e R09: fffffbfff1ce7046
R10: 0000000000000000 R11: dffffc0000000001 R12: ffff88807da5b8c0
R13: dffffc0000000000 R14: ffff888051e1801c R15: ffff888075b5e678
FS: 00007ff1cad826c0(0000) GS:ffff8880b9900000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007ff1c081f000 CR3: 0000000017e75000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
udf_prealloc_extents fs/udf/inode.c:1022 [inline]
inode_getblk fs/udf/inode.c:881 [inline]
udf_get_block+0x268c/0x5360 fs/udf/inode.c:449
__block_write_begin_int+0x544/0x1a30 fs/buffer.c:1991
__block_write_begin fs/buffer.c:2041 [inline]
block_write_begin+0x98/0x1f0 fs/buffer.c:2102
udf_write_begin+0x2d/0x60 fs/udf/inode.c:212
generic_perform_write+0x2fc/0x5e0 mm/filemap.c:3817
__generic_file_write_iter+0x176/0x400 mm/filemap.c:3945
udf_file_write_iter+0x291/0x670 fs/udf/file.c:164
call_write_iter include/linux/fs.h:2265 [inline]
new_sync_write fs/read_write.c:491 [inline]
vfs_write+0x7ae/0xba0 fs/read_write.c:584
ksys_write+0x19c/0x2c0 fs/read_write.c:637
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x3b/0xb0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7ff1ca07dd69
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 e1 20 00 00 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ff1cad820c8 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 00007ff1ca1abf80 RCX: 00007ff1ca07dd69
RDX: 0000000000010010 RSI: 000000002000e0c0 RDI: 000000000000000a
RBP: 00007ff1ca0ca49e R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 000000000000000b R14: 00007ff1ca1abf80 R15: 00007ffc63da1538
</TASK>


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