KCSAN: data-race in has_bh_in_lru / invalidate_bh_lru (2)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 4de593fb965f Merge tag 'net-5.15-rc4' of git://git.kernel...
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=15aaebdf300000
kernel config: https://syzkaller.appspot.com/x/.config?x=d39e13a59f87ee4d
dashboard link: https://syzkaller.appspot.com/bug?extid=aea2daf492f8a5b182aa
compiler: Debian clang version 11.0.1-2, GNU ld (GNU Binutils for Debian) 2.35.1
CC: [linux-...@vger.kernel.org linux-...@vger.kernel.org vi...@zeniv.linux.org.uk]

Unfortunately, I don't have any reproducer for this issue yet.

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

loop3: detected capacity change from 0 to 264192
EXT4-fs: Invalid sb specification: sb=0x0000000000000000",errors=continue
==================================================================
BUG: KCSAN: data-race in has_bh_in_lru / invalidate_bh_lru

write to 0xffff888237d22f10 of 8 bytes by task 29775 on cpu 1:
__invalidate_bh_lrus fs/buffer.c:1393 [inline]
invalidate_bh_lru+0x8d/0xc0 fs/buffer.c:1405
smp_call_function_many_cond+0x496/0x620 kernel/smp.c:960
on_each_cpu_cond_mask+0x31/0x40 kernel/smp.c:1135
on_each_cpu_cond include/linux/smp.h:105 [inline]
invalidate_bh_lrus+0x26/0x30 fs/buffer.c:1424
kill_bdev block/bdev.c:76 [inline]
blkdev_flush_mapping+0xd4/0x240 block/bdev.c:658
blkdev_put_whole block/bdev.c:689 [inline]
blkdev_put+0x3ab/0x4c0 block/bdev.c:953
blkdev_close+0x45/0x50 block/fops.c:460
__fput+0x295/0x520 fs/file_table.c:280
____fput+0x11/0x20 fs/file_table.c:313
task_work_run+0xae/0x130 kernel/task_work.c:164
tracehook_notify_resume include/linux/tracehook.h:189 [inline]
exit_to_user_mode_loop kernel/entry/common.c:175 [inline]
exit_to_user_mode_prepare+0x156/0x190 kernel/entry/common.c:207
__syscall_exit_to_user_mode_work kernel/entry/common.c:289 [inline]
syscall_exit_to_user_mode+0x20/0x40 kernel/entry/common.c:300
do_syscall_64+0x50/0xa0 arch/x86/entry/common.c:86
entry_SYSCALL_64_after_hwframe+0x44/0xae

read to 0xffff888237d22f10 of 8 bytes by task 29777 on cpu 0:
has_bh_in_lru+0x31/0x1c0 fs/buffer.c:1415
smp_call_function_many_cond+0x236/0x620 kernel/smp.c:917
on_each_cpu_cond_mask+0x31/0x40 kernel/smp.c:1135
on_each_cpu_cond include/linux/smp.h:105 [inline]
invalidate_bh_lrus+0x26/0x30 fs/buffer.c:1424
kill_bdev block/bdev.c:76 [inline]
set_blocksize+0x242/0x270 block/bdev.c:157
sb_set_blocksize block/bdev.c:166 [inline]
sb_min_blocksize+0x9d/0x120 block/bdev.c:182
ext4_fill_super+0x3a5/0x7840 fs/ext4/super.c:3918
mount_bdev+0x1e8/0x290 fs/super.c:1368
ext4_mount+0x2d/0x40 fs/ext4/super.c:6506
legacy_get_tree+0x70/0xc0 fs/fs_context.c:610
vfs_get_tree+0x4a/0x1a0 fs/super.c:1498
do_new_mount fs/namespace.c:2988 [inline]
path_mount+0x11ec/0x1d20 fs/namespace.c:3318
do_mount fs/namespace.c:3331 [inline]
__do_sys_mount fs/namespace.c:3539 [inline]
__se_sys_mount+0x24b/0x2f0 fs/namespace.c:3516
__x64_sys_mount+0x63/0x70 fs/namespace.c:3516
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: 0xffff888105d02750 -> 0x0000000000000000

Reported by Kernel Concurrency Sanitizer on:
CPU: 0 PID: 29777 Comm: syz-executor.3 Not tainted 5.15.0-rc3-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
==================================================================
EXT4-fs (loop3): VFS: Can't find ext4 filesystem
loop3: detected capacity change from 0 to 264192
EXT4-fs: Invalid sb specification: sb=0x0000000000000000",errors=continue
EXT4-fs (loop3): VFS: Can't find ext4 filesystem


---
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.

[syzbot]

Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.