[v5.15] WARNING in udf_new_block

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: c52b9710c83d Linux 5.15.156
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=159886c3180000
kernel config: https://syzkaller.appspot.com/x/.config?x=567b6ddc38438433
dashboard link: https://syzkaller.appspot.com/bug?extid=8cded13d88d44440ebdb
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/1bd4b9969373/disk-c52b9710.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/10509e89bd25/vmlinux-c52b9710.xz
kernel image: https://storage.googleapis.com/syzbot-assets/a623a4c52eb5/bzImage-c52b9710.xz

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

WARNING: CPU: 1 PID: 5302 at fs/udf/udfdecl.h:116 udf_add_free_space fs/udf/balloc.c:125 [inline]
WARNING: CPU: 1 PID: 5302 at fs/udf/udfdecl.h:116 udf_table_new_block fs/udf/balloc.c:667 [inline]
WARNING: CPU: 1 PID: 5302 at fs/udf/udfdecl.h:116 udf_new_block+0x1e2b/0x21a0 fs/udf/balloc.c:733
Modules linked in:
CPU: 1 PID: 5302 Comm: syz-executor.1 Not tainted 5.15.156-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/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_new_block fs/udf/balloc.c:667 [inline]
RIP: 0010:udf_new_block+0x1e2b/0x21a0 fs/udf/balloc.c:733
Code: fd ff ff e8 47 ad a7 fe 48 8b bc 24 80 00 00 00 e8 3a 59 4d 07 45 31 ff 48 8b 9c 24 98 00 00 00 e9 7d fd ff ff e8 25 ad a7 fe <0f> 0b 43 80 7c 25 00 00 0f 85 5e fc ff ff e9 61 fc ff ff 89 d9 80
RSP: 0018:ffffc90003197560 EFLAGS: 00010283
RAX: ffffffff82d8afbb RBX: 00000000bff8e25c RCX: 0000000000040000
RDX: ffffc9000de5d000 RSI: 0000000000001042 RDI: 0000000000001043
RBP: ffffc900031977b0 R08: ffffffff82d8ac12 R09: fffffbfff1bc8b5e
R10: 0000000000000000 R11: dffffc0000000001 R12: dffffc0000000000
R13: 1ffff1100faa14cf R14: ffff888059ef401c R15: ffff88807d50a678
FS: 00007f6e886a96c0(0000) GS:ffff8880b9b00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f7fb91af6e4 CR3: 000000004ffbf000 CR4: 00000000003506e0
Call Trace:
<TASK>
udf_new_inode+0x3a3/0xf10 fs/udf/ialloc.c:86
udf_create+0x1f/0x140 fs/udf/namei.c:612
lookup_open fs/namei.c:3462 [inline]
open_last_lookups fs/namei.c:3532 [inline]
path_openat+0x130a/0x2f20 fs/namei.c:3739
do_filp_open+0x21c/0x460 fs/namei.c:3769
do_sys_openat2+0x13b/0x500 fs/open.c:1253
do_sys_open fs/open.c:1269 [inline]
__do_sys_openat fs/open.c:1285 [inline]
__se_sys_openat fs/open.c:1280 [inline]
__x64_sys_openat+0x243/0x290 fs/open.c:1280
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x3b/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x66/0xd0
RIP: 0033:0x7f6e8a136ea9
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:00007f6e886a90c8 EFLAGS: 00000246 ORIG_RAX: 0000000000000101
RAX: ffffffffffffffda RBX: 00007f6e8a264f80 RCX: 00007f6e8a136ea9
RDX: 000000000000275a RSI: 0000000020000000 RDI: ffffffffffffff9c
RBP: 00007f6e8a1834a4 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 000000000000000b R14: 00007f6e8a264f80 R15: 00007ffe2fb798e8
</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