[moderation] [fs?] KCSAN: data-race in has_bh_in_lru / invalidate_bh_lrus_cpu (12)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 2f87d0916ce0 Merge tag 'trace-ringbuffer-v6.12-rc3' of git..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=10b4ac40580000
kernel config: https://syzkaller.appspot.com/x/.config?x=fd83253b74c9c570
dashboard link: https://syzkaller.appspot.com/bug?extid=ce96e6a573db7d932470
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
CC: [bra...@kernel.org ja...@suse.cz linux-...@vger.kernel.org linux-...@vger.kernel.org vi...@zeniv.linux.org.uk]

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/5dad7dfd22b7/disk-2f87d091.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/7d48173380b2/vmlinux-2f87d091.xz
kernel image: https://storage.googleapis.com/syzbot-assets/e987a6b34083/bzImage-2f87d091.xz

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

==================================================================
BUG: KCSAN: data-race in has_bh_in_lru / invalidate_bh_lrus_cpu

write to 0xffff888237d2bb10 of 8 bytes by task 979 on cpu 1:
__invalidate_bh_lrus fs/buffer.c:1505 [inline]
invalidate_bh_lrus_cpu+0x85/0xc0 fs/buffer.c:1550
lru_add_and_bh_lrus_drain mm/swap.c:759 [inline]
lru_add_drain_per_cpu+0x62/0x80 mm/swap.c:778
process_one_work kernel/workqueue.c:3229 [inline]
process_scheduled_works+0x483/0x9a0 kernel/workqueue.c:3310
worker_thread+0x51d/0x6f0 kernel/workqueue.c:3391
kthread+0x1d1/0x210 kernel/kthread.c:389
ret_from_fork+0x4b/0x60 arch/x86/kernel/process.c:147
ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244

read to 0xffff888237d2bb10 of 8 bytes by task 10271 on cpu 0:
has_bh_in_lru+0x35/0x1f0 fs/buffer.c:1527
smp_call_function_many_cond+0x2d5/0xc20 kernel/smp.c:837
on_each_cpu_cond_mask+0x3c/0x90 kernel/smp.c:1051
on_each_cpu_cond include/linux/smp.h:105 [inline]
invalidate_bh_lrus+0x2a/0x30 fs/buffer.c:1536
invalidate_bdev+0x42/0x70 block/bdev.c:100
loop_set_block_size drivers/block/loop.c:1471 [inline]
lo_simple_ioctl drivers/block/loop.c:1497 [inline]
lo_ioctl+0xb38/0x11c0 drivers/block/loop.c:1560
blkdev_ioctl+0x359/0x450 block/ioctl.c:693
vfs_ioctl fs/ioctl.c:51 [inline]
__do_sys_ioctl fs/ioctl.c:907 [inline]
__se_sys_ioctl+0xcd/0x140 fs/ioctl.c:893
__x64_sys_ioctl+0x43/0x50 fs/ioctl.c:893
x64_sys_call+0x15cc/0x2d60 arch/x86/include/generated/asm/syscalls_64.h:17
do_syscall_x64 arch/x86/entry/common.c:52 [inline]
do_syscall_64+0xc9/0x1c0 arch/x86/entry/common.c:83
entry_SYSCALL_64_after_hwframe+0x77/0x7f

value changed: 0x0000000000000000 -> 0xffff88811f0a5c30

Reported by Kernel Concurrency Sanitizer on:
CPU: 0 UID: 0 PID: 10271 Comm: syz.1.1784 Not tainted 6.12.0-rc3-syzkaller-00044-g2f87d0916ce0 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024
==================================================================
Invalid logical block size (65472)


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

If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup

[syzbot]

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