loop4: detected capacity change from 0 to 256
==================================================================
BUG: KCSAN: data-race in has_bh_in_lru / invalidate_bh_lru

write to 0xffff888237d2a378 of 8 bytes by task 3161 on cpu 1:
 __invalidate_bh_lrus fs/buffer.c:1424 [inline]
 invalidate_bh_lru+0x88/0xf0 fs/buffer.c:1436
 smp_call_function_many_cond+0x52e/0x6f0 kernel/smp.c:978
 on_each_cpu_cond_mask+0x3c/0x80 kernel/smp.c:1155
 on_each_cpu_cond include/linux/smp.h:105 [inline]
 invalidate_bh_lrus+0x2a/0x30 fs/buffer.c:1455
 kill_bdev block/bdev.c:75 [inline]
 blkdev_flush_mapping+0xb6/0x1c0 block/bdev.c:584
 blkdev_put_whole block/bdev.c:615 [inline]
 blkdev_put+0x36d/0x470 block/bdev.c:875
 kill_block_super+0x83/0xa0 fs/super.c:1410
 deactivate_locked_super+0x6b/0xd0 fs/super.c:331
 deactivate_super+0x9b/0xb0 fs/super.c:362
 cleanup_mnt+0x272/0x2e0 fs/namespace.c:1177
 __cleanup_mnt+0x19/0x20 fs/namespace.c:1184
 task_work_run+0x123/0x160 kernel/task_work.c:179
 resume_user_mode_work include/linux/resume_user_mode.h:49 [inline]
 exit_to_user_mode_loop+0xd1/0xe0 kernel/entry/common.c:171
 exit_to_user_mode_prepare+0x6c/0xb0 kernel/entry/common.c:204
 __syscall_exit_to_user_mode_work kernel/entry/common.c:286 [inline]
 syscall_exit_to_user_mode+0x26/0x140 kernel/entry/common.c:297
 do_syscall_64+0x4d/0xc0 arch/x86/entry/common.c:86
 entry_SYSCALL_64_after_hwframe+0x63/0xcd

read to 0xffff888237d2a378 of 8 bytes by task 471 on cpu 0:
 has_bh_in_lru+0x35/0x1e0 fs/buffer.c:1446
 smp_call_function_many_cond+0x2dd/0x6f0 kernel/smp.c:935
 on_each_cpu_cond_mask+0x3c/0x80 kernel/smp.c:1155
 on_each_cpu_cond include/linux/smp.h:105 [inline]
 invalidate_bh_lrus+0x2a/0x30 fs/buffer.c:1455
 kill_bdev block/bdev.c:75 [inline]
 set_blocksize+0x266/0x290 block/bdev.c:152
 sb_set_blocksize+0x2d/0xb0 block/bdev.c:161
 fat_fill_super+0x15d6/0x28e0 fs/fat/inode.c:1677
 msdos_fill_super+0x2d/0x40 fs/fat/namei_msdos.c:655
 mount_bdev+0x1e5/0x280 fs/super.c:1380
 msdos_mount+0x31/0x40 fs/fat/namei_msdos.c:662
 legacy_get_tree+0x74/0xd0 fs/fs_context.c:610
 vfs_get_tree+0x51/0x190 fs/super.c:1510
 do_new_mount+0x200/0x650 fs/namespace.c:3042
 path_mount+0x498/0xb40 fs/namespace.c:3372
 do_mount fs/namespace.c:3385 [inline]
 __do_sys_mount fs/namespace.c:3594 [inline]
 __se_sys_mount+0x27f/0x2d0 fs/namespace.c:3571
 __x64_sys_mount+0x67/0x80 fs/namespace.c:3571
 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: 0xffff8881024b6bc8 -> 0x0000000000000000

Reported by Kernel Concurrency Sanitizer on:
CPU: 0 PID: 471 Comm: syz-executor.4 Not tainted 6.3.0-rc5-syzkaller-00153-gaa318c48808c #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/30/2023
==================================================================
FAT-fs (loop4): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.