loop4: detected capacity change from 0 to 512
EXT4-fs (loop4): feature flags set on rev 0 fs, running e2fsck is recommended
==================================================================
BUG: KCSAN: data-race in data_alloc / data_push_tail

write to 0xffffffff86eb4b28 of 8 bytes by task 11034 on cpu 1:
 data_alloc+0x216/0x2c0 kernel/printk/printk_ringbuffer.c:1074
 prb_reserve+0x893/0xbc0 kernel/printk/printk_ringbuffer.c:1555
 vprintk_store+0x53e/0x800 kernel/printk/printk.c:2232
 vprintk_emit+0xd0/0x5d0 kernel/printk/printk.c:2288
 vprintk_default+0x26/0x30 kernel/printk/printk.c:2322
 vprintk+0x71/0x80 kernel/printk/printk_safe.c:45
 _printk+0x7a/0xa0 kernel/printk/printk.c:2332
 __ext4_error_inode+0x2d5/0x400 fs/ext4/super.c:861
 __ext4_iget+0x1c50/0x1e70
 __ext4_fill_super fs/ext4/super.c:5473 [inline]
 ext4_fill_super+0x2f0b/0x3940 fs/ext4/super.c:5703
 get_tree_bdev+0x272/0x300 fs/super.c:1577
 ext4_get_tree+0x1c/0x20 fs/ext4/super.c:5735
 vfs_get_tree+0x51/0x1b0 fs/super.c:1750
 do_new_mount+0x203/0x660 fs/namespace.c:3335
 path_mount+0x496/0xb30 fs/namespace.c:3662
 do_mount fs/namespace.c:3675 [inline]
 __do_sys_mount fs/namespace.c:3884 [inline]
 __se_sys_mount+0x27f/0x2d0 fs/namespace.c:3861
 __x64_sys_mount+0x67/0x80 fs/namespace.c:3861
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x41/0xc0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x63/0xcd

read to 0xffffffff86eb4b28 of 8 bytes by task 11040 on cpu 0:
 data_make_reusable kernel/printk/printk_ringbuffer.c:590 [inline]
 data_push_tail+0x102/0x430 kernel/printk/printk_ringbuffer.c:675
 data_alloc+0xbe/0x2c0 kernel/printk/printk_ringbuffer.c:1046
 prb_reserve+0x893/0xbc0 kernel/printk/printk_ringbuffer.c:1555
 vprintk_store+0x53e/0x800 kernel/printk/printk.c:2232
 vprintk_emit+0xd0/0x5d0 kernel/printk/printk.c:2288
 vprintk_default+0x26/0x30 kernel/printk/printk.c:2322
 vprintk+0x71/0x80 kernel/printk/printk_safe.c:45
 _printk+0x7a/0xa0 kernel/printk/printk.c:2332
 __ext4_msg+0x18a/0x1a0 fs/ext4/super.c:998
 ext4_check_feature_compatibility+0xde/0x5e0 fs/ext4/super.c:4664
 __ext4_fill_super fs/ext4/super.c:5283 [inline]
 ext4_fill_super+0x213c/0x3940 fs/ext4/super.c:5703
 get_tree_bdev+0x272/0x300 fs/super.c:1577
 ext4_get_tree+0x1c/0x20 fs/ext4/super.c:5735
 vfs_get_tree+0x51/0x1b0 fs/super.c:1750
 do_new_mount+0x203/0x660 fs/namespace.c:3335
 path_mount+0x496/0xb30 fs/namespace.c:3662
 do_mount fs/namespace.c:3675 [inline]
 __do_sys_mount fs/namespace.c:3884 [inline]
 __se_sys_mount+0x27f/0x2d0 fs/namespace.c:3861
 __x64_sys_mount+0x67/0x80 fs/namespace.c:3861
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x41/0xc0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x63/0xcd

value changed: 0x00000001000196f1 -> 0x000000010001a322

Reported by Kernel Concurrency Sanitizer on:
CPU: 0 PID: 11040 Comm: syz-executor.4 Not tainted 6.6.0-rc4-syzkaller-00029-gcbf3a2cb156a #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/06/2023
==================================================================
EXT4-fs error (device loop4): ext4_init_orphan_info:586: comm syz-executor.4: inode #0: comm syz-executor.4: iget: illegal inode #
EXT4-fs (loop4): Remounting filesystem read-only
EXT4-fs (loop4): get orphan inode failed
EXT4-fs (loop4): mount failed