================================================================== BUG: KCSAN: data-race in ext4_mb_find_by_goal / mb_mark_used write to 0xffff8881010e0494 of 4 bytes by task 623 on cpu 0: mb_mark_used+0x13b/0xc50 fs/ext4/mballoc.c:1947 ext4_mb_use_best_found+0x102/0x320 fs/ext4/mballoc.c:2019 ext4_mb_simple_scan_group+0x253/0x3a0 fs/ext4/mballoc.c:2297 ext4_mb_regular_allocator+0x1984/0x2530 fs/ext4/mballoc.c:2773 ext4_mb_new_blocks+0x792/0x1fc0 fs/ext4/mballoc.c:5586 ext4_ext_map_blocks+0x15ed/0x1ff0 fs/ext4/extents.c:4250 ext4_map_blocks+0x71e/0xf00 fs/ext4/inode.c:637 ext4_alloc_file_blocks+0x281/0x730 fs/ext4/extents.c:4437 ext4_fallocate+0x2a7/0x4d0 fs/ext4/extents.c:4718 vfs_fallocate+0x459/0x6a0 fs/open.c:307 ksys_fallocate fs/open.c:330 [inline] __do_sys_fallocate fs/open.c:338 [inline] __se_sys_fallocate fs/open.c:336 [inline] __x64_sys_fallocate+0x75/0xc0 fs/open.c:336 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x44/0xa0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x44/0xae read to 0xffff8881010e0494 of 4 bytes by task 594 on cpu 1: ext4_mb_find_by_goal+0x13a/0x8a0 fs/ext4/mballoc.c:2207 ext4_mb_regular_allocator+0x130/0x2530 fs/ext4/mballoc.c:2654 ext4_mb_new_blocks+0x792/0x1fc0 fs/ext4/mballoc.c:5586 ext4_ext_map_blocks+0x15ed/0x1ff0 fs/ext4/extents.c:4250 ext4_map_blocks+0x71e/0xf00 fs/ext4/inode.c:637 ext4_alloc_file_blocks+0x281/0x730 fs/ext4/extents.c:4437 ext4_fallocate+0x2a7/0x4d0 fs/ext4/extents.c:4718 vfs_fallocate+0x459/0x6a0 fs/open.c:307 ksys_fallocate fs/open.c:330 [inline] __do_sys_fallocate fs/open.c:338 [inline] __se_sys_fallocate fs/open.c:336 [inline] __x64_sys_fallocate+0x75/0xc0 fs/open.c:336 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x44/0xa0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x44/0xae value changed: 0x000027f5 -> 0x00001ff5 Reported by Kernel Concurrency Sanitizer on: CPU: 1 PID: 594 Comm: syz-executor.5 Not tainted 5.14.0-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 ==================================================================