[v5.15] WARNING in udf_free_blocks (2)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 4735586da88e Linux 5.15.176
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=13c2abc4580000
kernel config: https://syzkaller.appspot.com/x/.config?x=8c3b695ffd9247a0
dashboard link: https://syzkaller.appspot.com/bug?extid=eee8568c73f195a7d8fa
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=16780a18580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=11d4bf0f980000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/44a9faa53b37/disk-4735586d.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/2e4ec21926b2/vmlinux-4735586d.xz
kernel image: https://storage.googleapis.com/syzbot-assets/f96f554b1d28/bzImage-4735586d.xz
mounted in repro #1: https://storage.googleapis.com/syzbot-assets/2e6cf84981c6/mount_0.gz
mounted in repro #2: https://storage.googleapis.com/syzbot-assets/27c7d413f5cd/mount_1.gz

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

------------[ cut here ]------------
WARNING: CPU: 1 PID: 4162 at fs/udf/udfdecl.h:127 udf_add_free_space fs/udf/balloc.c:137 [inline]
WARNING: CPU: 1 PID: 4162 at fs/udf/udfdecl.h:127 udf_bitmap_free_blocks fs/udf/balloc.c:183 [inline]
WARNING: CPU: 1 PID: 4162 at fs/udf/udfdecl.h:127 udf_free_blocks+0x7ff/0x21e0 fs/udf/balloc.c:683
Modules linked in:
CPU: 1 PID: 4162 Comm: syz-executor136 Not tainted 5.15.176-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024
RIP: 0010:udf_updated_lvid fs/udf/udfdecl.h:125 [inline]
RIP: 0010:udf_add_free_space fs/udf/balloc.c:137 [inline]
RIP: 0010:udf_bitmap_free_blocks fs/udf/balloc.c:183 [inline]
RIP: 0010:udf_free_blocks+0x7ff/0x21e0 fs/udf/balloc.c:683
Code: 24 d0 00 00 00 0f 83 5f 03 00 00 4c 01 64 24 20 e8 96 0d 9d fe 48 8b 84 24 c0 00 00 00 41 89 c4 e9 3d fb ff ff e8 81 0d 9d fe <0f> 0b e9 6b ff ff ff 48 8b 4c 24 48 80 e1 07 38 c1 0f 8c 36 fb ff
RSP: 0018:ffffc90002dbf560 EFLAGS: 00010293
RAX: ffffffff82e3775f RBX: 00000000f7f1c71c RCX: ffff88801e661dc0
RDX: 0000000000000000 RSI: 00000000f7f1c71c RDI: 0000000000000000
RBP: ffffc90002dbf770 R08: ffffffff82e376c4 R09: ffffed100e29ce04
R10: 0000000000000000 R11: dffffc0000000001 R12: 0000000000000003
R13: dffffc0000000000 R14: 0000000000000000 R15: ffff888073b7c01c
FS: 000055558eea0380(0000) GS:ffff8880b8f00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fff3a889ff8 CR3: 000000006e83d000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
extent_trunc+0x38c/0x4a0 fs/udf/truncate.c:56
udf_truncate_extents+0x3f6/0x11a0 fs/udf/truncate.c:212
udf_setsize+0x100a/0x1430 fs/udf/inode.c:1183
udf_evict_inode+0x79/0x3d0 fs/udf/inode.c:145
evict+0x529/0x930 fs/inode.c:622
do_unlinkat+0x508/0x950 fs/namei.c:4355
__do_sys_unlink fs/namei.c:4396 [inline]
__se_sys_unlink fs/namei.c:4394 [inline]
__x64_sys_unlink+0x45/0x50 fs/namei.c:4394
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:0x7f4f71f5dd57
Code: 73 01 c3 48 c7 c1 b8 ff ff ff f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 b8 57 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fff3a88a2a8 EFLAGS: 00000206 ORIG_RAX: 0000000000000057
RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007f4f71f5dd57
RDX: 00007fff3a88a2d0 RSI: 00007fff3a88a360 RDI: 00007fff3a88a360
RBP: 00007fff3a88a360 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000100 R11: 0000000000000206 R12: 00007fff3a88b450
R13: 000055558eeb1740 R14: 431bde82d7b634db R15: 00007fff3a88d5d0
</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 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 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