[v5.15] WARNING in udf_free_blocks

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 284087d4f7d5 Linux 5.15.158
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=12d0f600980000
kernel config: https://syzkaller.appspot.com/x/.config?x=b0dd54e4b5171ebc
dashboard link: https://syzkaller.appspot.com/bug?extid=ace91214f35aa808e786
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/c2e33c1db6bf/disk-284087d4.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/d9f77284af1d/vmlinux-284087d4.xz
kernel image: https://storage.googleapis.com/syzbot-assets/a600323dd149/bzImage-284087d4.xz

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

------------[ cut here ]------------
WARNING: CPU: 0 PID: 9440 at fs/udf/udfdecl.h:116 udf_add_free_space fs/udf/balloc.c:125 [inline]
WARNING: CPU: 0 PID: 9440 at fs/udf/udfdecl.h:116 udf_table_free_blocks fs/udf/balloc.c:407 [inline]
WARNING: CPU: 0 PID: 9440 at fs/udf/udfdecl.h:116 udf_free_blocks+0x1d4a/0x23a0 fs/udf/balloc.c:685
Modules linked in:
CPU: 0 PID: 9440 Comm: syz-executor.2 Not tainted 5.15.158-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_free_blocks fs/udf/balloc.c:407 [inline]
RIP: 0010:udf_free_blocks+0x1d4a/0x23a0 fs/udf/balloc.c:685
Code: 00 00 e8 99 a9 f1 fe 48 8b 9c 24 70 01 00 00 48 85 db 74 07 e8 67 d1 a7 fe eb b7 e8 60 d1 a7 fe e9 52 e7 ff ff e8 56 d1 a7 fe <0f> 0b e9 47 ef ff ff 89 d9 80 e1 07 fe c1 38 c1 0f 8c 7c e3 ff ff
RSP: 0018:ffffc90002ec7a00 EFLAGS: 00010293
RAX: ffffffff82d88b6a RBX: 00000000831b1a36 RCX: ffff888018f68000
RDX: 0000000000000000 RSI: 00000000831b1a36 RDI: 0000000000000000
RBP: ffffc90002ec7c10 R08: ffffffff82d87aab R09: fffff520005d8efd
R10: 0000000000000000 R11: dffffc0000000001 R12: ffff88805f21e4c0
R13: dffffc0000000000 R14: ffff888066f2201c R15: ffff8880608ae000
FS: 0000555555951480(0000) GS:ffff8880b9a00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000001b3312e000 CR3: 0000000064284000 CR4: 00000000003526f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
udf_discard_prealloc+0x55c/0x860 fs/udf/truncate.c:151
udf_release_file+0xb8/0x120 fs/udf/file.c:235
__fput+0x3bf/0x890 fs/file_table.c:280
task_work_run+0x129/0x1a0 kernel/task_work.c:164
tracehook_notify_resume include/linux/tracehook.h:189 [inline]
exit_to_user_mode_loop+0x106/0x130 kernel/entry/common.c:181
exit_to_user_mode_prepare+0xb1/0x140 kernel/entry/common.c:214
__syscall_exit_to_user_mode_work kernel/entry/common.c:296 [inline]
syscall_exit_to_user_mode+0x5d/0x240 kernel/entry/common.c:307
do_syscall_64+0x47/0xb0 arch/x86/entry/common.c:86
entry_SYSCALL_64_after_hwframe+0x66/0xd0
RIP: 0033:0x7f1eee50cc5a
Code: 48 3d 00 f0 ff ff 77 48 c3 0f 1f 80 00 00 00 00 48 83 ec 18 89 7c 24 0c e8 03 7f 02 00 8b 7c 24 0c 89 c2 b8 03 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 36 89 d7 89 44 24 0c e8 63 7f 02 00 8b 44 24
RSP: 002b:00007ffe49daa590 EFLAGS: 00000293 ORIG_RAX: 0000000000000003
RAX: 0000000000000000 RBX: 0000000000000008 RCX: 00007f1eee50cc5a
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000007
RBP: 00007f1eee63d980 R08: 0000001b33520000 R09: 0000000000001211
R10: 0000000083f68a4a R11: 0000000000000293 R12: 000000000004ee24
R13: 00007f1eee63c05c R14: 00007f1eee63c050 R15: 0000000000000032
</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