loop9: detected capacity change from 0 to 512
EXT4-fs error (device loop9): ext4_get_journal_inode:5927: comm syz.9.4717: inode #2147418112: comm syz.9.4717: iget: illegal inode #
loop9: lost filesystem error report for type 5 error -117
==================================================================
BUG: KCSAN: data-race in _copy_to_iter / memcpy_and_pad

read to 0xffff88811b9c7400 of 1024 bytes by task 12070 on cpu 0:
 instrument_copy_to_user include/linux/instrumented.h:130 [inline]
 copy_to_user_iter lib/iov_iter.c:24 [inline]
 iterate_ubuf include/linux/iov_iter.h:30 [inline]
 iterate_and_advance2 include/linux/iov_iter.h:302 [inline]
 iterate_and_advance include/linux/iov_iter.h:330 [inline]
 _copy_to_iter+0x130/0xea0 lib/iov_iter.c:197
 copy_page_to_iter+0x174/0x210 lib/iov_iter.c:374
 copy_folio_to_iter include/linux/uio.h:204 [inline]
 filemap_read+0x3fd/0xad0 mm/filemap.c:2875
 blkdev_read_iter+0x21e/0x2d0 block/fops.c:832
 new_sync_read fs/read_write.c:493 [inline]
 vfs_read+0x699/0x7c0 fs/read_write.c:574
 ksys_read+0xdc/0x1a0 fs/read_write.c:716
 __do_sys_read fs/read_write.c:725 [inline]
 __se_sys_read fs/read_write.c:723 [inline]
 __x64_sys_read+0x40/0x50 fs/read_write.c:723
 x64_sys_call+0x2135/0x2550 arch/x86/include/generated/asm/syscalls_64.h:1
 do_syscall_x64 arch/x86/entry/syscall_64.c:61 [inline]
 do_syscall_64+0x112/0x360 arch/x86/entry/syscall_64.c:84
 entry_SYSCALL_64_after_hwframe+0x77/0x7f

write to 0xffff88811b9c75f6 of 10 bytes by task 14812 on cpu 1:
 memcpy_and_pad+0x5a/0x80 lib/string_helpers.c:1009
 ext4_update_super+0x790/0xba0 fs/ext4/super.c:6303
 ext4_commit_super+0x40/0x260 fs/ext4/super.c:6332
 ext4_handle_error+0x46f/0x570 fs/ext4/super.c:725
 __ext4_error+0x172/0x2e0 fs/ext4/super.c:837
 __ext4_iget+0x4c1/0x2360 fs/ext4/inode.c:5339
 ext4_get_journal_inode+0x2a/0x130 fs/ext4/super.c:5927
 ext4_calculate_overhead+0x933/0xa20 fs/ext4/super.c:4294
 __ext4_fill_super fs/ext4/super.c:5599 [inline]
 ext4_fill_super+0x2838/0x37b0 fs/ext4/super.c:5855
 get_tree_bdev_flags+0x291/0x300 fs/super.c:1873
 get_tree_bdev+0x1f/0x30 fs/super.c:1896
 ext4_get_tree+0x1c/0x30 fs/ext4/super.c:5887
 vfs_get_tree+0x57/0x1d0 fs/super.c:1933
 fc_mount fs/namespace.c:1198 [inline]
 do_new_mount_fc fs/namespace.c:3772 [inline]
 do_new_mount+0x288/0x8d0 fs/namespace.c:3848
 path_mount+0x4ad/0xb90 fs/namespace.c:4168
 do_mount fs/namespace.c:4181 [inline]
 __do_sys_mount fs/namespace.c:4397 [inline]
 __se_sys_mount+0x28c/0x2e0 fs/namespace.c:4374
 __x64_sys_mount+0x67/0x80 fs/namespace.c:4374
 x64_sys_call+0xc3b/0x2550 arch/x86/include/generated/asm/syscalls_64.h:166
 do_syscall_x64 arch/x86/entry/syscall_64.c:61 [inline]
 do_syscall_64+0x112/0x360 arch/x86/entry/syscall_64.c:84
 entry_SYSCALL_64_after_hwframe+0x77/0x7f

Reported by Kernel Concurrency Sanitizer on:
CPU: 1 UID: 0 PID: 14812 Comm: syz.9.4717 Not tainted syzkaller #0 PREEMPT(lazy) 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/24/2026
==================================================================
EXT4-fs (loop9): no journal found
EXT4-fs (loop9): can't get journal size
EXT4-fs (loop9): warning: mounting fs with errors, running e2fsck is recommended
EXT4-fs (loop9): Errors on filesystem, clearing orphan list.
vhci_hcd vhci_hcd.2: invalid port number 254
vhci_hcd vhci_hcd.2: invalid port number 254