[v5.15] WARNING in __udf_add_aext

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: f6f7927ac664 Linux 5.15.127
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1698dba0680000
kernel config: https://syzkaller.appspot.com/x/.config?x=ea39ec6ccd2c5d32
dashboard link: https://syzkaller.appspot.com/bug?extid=6a9661c8887dbe7bd474
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=1083be4ba80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16941e5fa80000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/e290f46611c7/disk-f6f7927a.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/64ee0ddb7c8c/vmlinux-f6f7927a.xz
kernel image: https://storage.googleapis.com/syzbot-assets/3c32675f93c1/bzImage-f6f7927a.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/48d7579addf3/mount_0.gz

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

UDF-fs: error (device loop0): udf_read_tagged: tag checksum failed, block 99: 0x27 != 0x4d
UDF-fs: INFO Mounting volume 'LinuxUDF', timestamp 2022/11/22 14:59 (1000)
------------[ cut here ]------------
WARNING: CPU: 1 PID: 3495 at fs/udf/inode.c:2015 __udf_add_aext+0x54c/0x6f0
Modules linked in:
CPU: 1 PID: 3495 Comm: syz-executor251 Not tainted 5.15.127-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/26/2023
RIP: 0010:__udf_add_aext+0x54c/0x6f0 fs/udf/inode.c:2014
Code: 4c 89 e7 e8 66 65 f1 fe 49 8b 3c 24 4c 89 fe e8 0a bb 0c ff 31 c0 48 83 c4 30 5b 41 5c 41 5d 41 5e 41 5f 5d c3 e8 54 c5 a7 fe <0f> 0b e9 ed fb ff ff e8 48 c5 a7 fe 0f 0b e9 5c fc ff ff e8 3c c5
RSP: 0018:ffffc900011df118 EFLAGS: 00010293
RAX: ffffffff82d84e8c RBX: 1ffff9200023bee1 RCX: ffff8880784e3b80
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 00000000000001d0
RBP: 00000000000001d0 R08: ffffffff82d84a72 R09: ffffffff82d849a2
R10: 0000000000000002 R11: ffff8880784e3b80 R12: ffffc900011df700
R13: 0000000000000000 R14: dffffc0000000000 R15: ffffc900011df708
FS: 0000555555aa3380(0000) GS:ffff8880b9a00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000559ccaca3e30 CR3: 00000000708c6000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
udf_setup_indirect_aext+0x6bc/0x980 fs/udf/inode.c:1980
udf_add_aext fs/udf/inode.c:2067 [inline]
udf_do_extend_file+0x6df/0x1140 fs/udf/inode.c:562
inode_getblk fs/udf/inode.c:798 [inline]
udf_get_block+0x1520/0x4d10 fs/udf/inode.c:448
__block_write_begin_int+0x60b/0x1650 fs/buffer.c:2012
__block_write_begin fs/buffer.c:2062 [inline]
block_write_begin+0x4f/0xc0 fs/buffer.c:2122
udf_write_begin+0x36/0x70 fs/udf/inode.c:212
generic_perform_write+0x2bf/0x5b0 mm/filemap.c:3776
__generic_file_write_iter+0x243/0x4f0 mm/filemap.c:3903
udf_file_write_iter+0x28d/0x530 fs/udf/file.c:163
call_write_iter include/linux/fs.h:2103 [inline]
new_sync_write fs/read_write.c:507 [inline]
vfs_write+0xacf/0xe50 fs/read_write.c:594
ksys_pwrite64 fs/read_write.c:701 [inline]
__do_sys_pwrite64 fs/read_write.c:711 [inline]
__se_sys_pwrite64 fs/read_write.c:708 [inline]
__x64_sys_pwrite64+0x1a9/0x230 fs/read_write.c:708
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+0x61/0xcb
RIP: 0033:0x7efcdc573679
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 61 17 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 b8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fff0c222098 EFLAGS: 00000246 ORIG_RAX: 0000000000000012
RAX: ffffffffffffffda RBX: 00007fff0c222268 RCX: 00007efcdc573679
RDX: 0000000000000001 RSI: 0000000020000180 RDI: 0000000000000004
RBP: 00007efcdc5e7610 R08: 0000000000000000 R09: 00007fff0c222268
R10: 000004010040bffd R11: 0000000000000246 R12: 0000000000000001
R13: 00007fff0c222258 R14: 0000000000000001 R15: 0000000000000001
</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

[syzbot]

syzbot suspects this issue could be fixed by backporting the following commit:

commit c2efd13a2ed4f29bf9ef14ac2fbb7474084655f8
git tree: upstream
Author: Jan Kara <ja...@suse.cz>
Date: Wed Jan 25 16:56:06 2023 +0000

udf: Limit file size to 4TB

bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=172b4145e80000

kernel config: https://syzkaller.appspot.com/x/.config?x=ea39ec6ccd2c5d32
dashboard link: https://syzkaller.appspot.com/bug?extid=6a9661c8887dbe7bd474

syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1083be4ba80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16941e5fa80000

Please keep in mind that other backports might be required as well.

For information about bisection process see: https://goo.gl/tpsmEJ#bisection