[v5.15] WARNING in udf_free_inode

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: f45bea23c39c Linux 5.15.162
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=16df9c9e980000
kernel config: https://syzkaller.appspot.com/x/.config?x=e4bf7e31dc0c0a74
dashboard link: https://syzkaller.appspot.com/bug?extid=99421c2e931ac778e38a
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/4d8c24af3786/disk-f45bea23.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/e3446b6ec2ee/vmlinux-f45bea23.xz
kernel image: https://storage.googleapis.com/syzbot-assets/0fb8209336b0/bzImage-f45bea23.xz

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

WARNING: CPU: 1 PID: 3626 at fs/udf/udfdecl.h:116 udf_free_inode+0x230/0x2d0 fs/udf/ialloc.c:41
Modules linked in:
CPU: 1 PID: 3626 Comm: syz.4.15 Not tainted 5.15.162-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/07/2024
RIP: 0010:udf_updated_lvid fs/udf/udfdecl.h:114 [inline]
RIP: 0010:udf_free_inode+0x230/0x2d0 fs/udf/ialloc.c:41
Code: ff ff 4c 89 f7 31 f6 4c 89 ea 31 c9 41 b8 01 00 00 00 48 83 c4 20 5b 41 5c 41 5d 41 5e 41 5f 5d e9 85 62 ff ff e8 60 50 a7 fe <0f> 0b e9 7c ff ff ff 44 89 e9 80 e1 07 fe c1 38 c1 0f 8c 5e fe ff
RSP: 0018:ffffc900032b7c78 EFLAGS: 00010293
RAX: ffffffff82d90b00 RBX: 00000000e2d4e8e2 RCX: ffff88807b605940
RDX: 0000000000000000 RSI: 00000000e2d4e8e2 RDI: 0000000000000000
RBP: ffff88801a2fe01f R08: ffffffff82d90a75 R09: fffff52000656f4d
R10: 0000000000000000 R11: dffffc0000000001 R12: 1ffff1100f70dccf
R13: ffff8880628887c0 R14: ffff88807b86e000 R15: ffff88807b86e678
FS: 0000555555acd500(0000) GS:ffff8880b9a00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000563f73b6fc08 CR3: 000000001d4e6000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
evict+0x2a4/0x620 fs/inode.c:587
__dentry_kill+0x436/0x650 fs/dcache.c:582
dentry_kill+0xbb/0x290
dput+0xd8/0x1a0 fs/dcache.c:889
__fput+0x5ec/0x890 fs/file_table.c:288
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:0x7fe2e2dc4bd9
Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 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 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fffd93eec18 EFLAGS: 00000246 ORIG_RAX: 00000000000001b4
RAX: 0000000000000000 RBX: 000000000000cbc1 RCX: 00007fe2e2dc4bd9
RDX: 0000000000000000 RSI: 000000000000001e RDI: 0000000000000003
RBP: ffffffffffffffff R08: 0000000000000001 R09: 0000001ed93eef4f
R10: 00007fe2e2c4f000 R11: 0000000000000246 R12: 00007fe2e2f52f6c
R13: 0000000000000032 R14: 00007fe2e2f54a60 R15: 00007fe2e2f52f60
</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