[v6.1] WARNING in udf_setsize

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 09045dae0d90 Linux 6.1.53
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=155201ac680000
kernel config: https://syzkaller.appspot.com/x/.config?x=195b6ef285251409
dashboard link: https://syzkaller.appspot.com/bug?extid=cd0fdf627e8dc19260f1
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=178c55a0680000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=14430418680000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/c3b1bb820e74/disk-09045dae.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/4c5cfb0563d9/vmlinux-09045dae.xz
kernel image: https://storage.googleapis.com/syzbot-assets/c682edb60d96/bzImage-09045dae.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/bea401078320/mount_0.gz

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

loop0: detected capacity change from 0 to 2048
UDF-fs: INFO Mounting volume 'LinuxUDF', timestamp 2022/11/22 14:59 (1000)
------------[ cut here ]------------
WARNING: CPU: 0 PID: 4150 at fs/udf/inode.c:651 udf_setsize+0x103d/0x1430 fs/udf/inode.c:1241
Modules linked in:
CPU: 0 PID: 4150 Comm: syz-executor303 Not tainted 6.1.53-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/04/2023
RIP: 0010:udf_extend_file fs/udf/inode.c:650 [inline]
RIP: 0010:udf_setsize+0x103d/0x1430 fs/udf/inode.c:1241
Code: 6e fe 31 ff 44 89 e6 e8 41 1e 8f fe 45 85 e4 74 0a e8 d7 1a 8f fe e9 2a ff ff ff e8 cd 1a 8f fe e9 e7 fd ff ff e8 c3 1a 8f fe <0f> 0b e9 5e f6 ff ff 89 d9 80 e1 07 38 c1 0f 8c 7e f0 ff ff 48 89
RSP: 0018:ffffc90003fefb00 EFLAGS: 00010293
RAX: ffffffff82faf96d RBX: 0000000000000200 RCX: ffff888028f71dc0
RDX: 0000000000000000 RSI: 0000000000000400 RDI: 0000000000000200
RBP: ffffc90003fefcd8 R08: ffffffff82faefae R09: ffffed100e0fa358
R10: 0000000000000000 R11: dffffc0000000001 R12: 0000000000000009
R13: 1ffff920007fdf70 R14: 0000000000000400 R15: 0000000000000002
FS: 00007fd4392e06c0(0000) GS:ffff8880b9800000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fd430fbfd58 CR3: 000000001fd99000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
udf_setattr+0x36c/0x540 fs/udf/file.c:279
notify_change+0xdcd/0x1080 fs/attr.c:483
do_truncate+0x21c/0x300 fs/open.c:65
do_sys_ftruncate+0x2e2/0x380 fs/open.c:193
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7fd439323b59
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 b1 18 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:00007fd4392e0218 EFLAGS: 00000246 ORIG_RAX: 000000000000004d
RAX: ffffffffffffffda RBX: 00007fd4393ac6c8 RCX: 00007fd439323b59
RDX: 00007fd439323b59 RSI: 0000000000000002 RDI: 0000000000000004
RBP: 00007fd4393ac6c0 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00007fd439378e00
R13: 00007fd439378208 R14: 00007fd4393780c0 R15: 0030656c69662f2e
</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 bug is already fixed, 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 bug's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the bug is a duplicate of another bug, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup