[moderation] [block?] KCSAN: data-race in blk_mq_dispatch_rq_list / blk_mq_dispatch_rq_list (7)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 7c16f0a4ed1c Merge tag 'i2c-for-6.10-rc5' of git://git.ker..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=11bfff56980000
kernel config: https://syzkaller.appspot.com/x/.config?x=704451bc2941bcb0
dashboard link: https://syzkaller.appspot.com/bug?extid=cd59997629d2514141ae
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
CC: [ax...@kernel.dk linux...@vger.kernel.org linux-...@vger.kernel.org]

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/9acd4869df3e/disk-7c16f0a4.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/a5b6e853a6e5/vmlinux-7c16f0a4.xz
kernel image: https://storage.googleapis.com/syzbot-assets/23b225386827/bzImage-7c16f0a4.xz

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

==================================================================
BUG: KCSAN: data-race in blk_mq_dispatch_rq_list / blk_mq_dispatch_rq_list

read to 0xffff888100e4f0f8 of 4 bytes by task 46 on cpu 1:
blk_mq_update_dispatch_busy block/blk-mq.c:1900 [inline]
blk_mq_dispatch_rq_list+0xd0f/0xf30 block/blk-mq.c:2121
__blk_mq_sched_dispatch_requests+0x1ce/0xd50 block/blk-mq-sched.c:301
blk_mq_sched_dispatch_requests+0x78/0xe0 block/blk-mq-sched.c:331
blk_mq_run_hw_queue+0x29c/0x4d0 block/blk-mq.c:2250
blk_mq_run_hw_queues+0x15b/0x1e0 block/blk-mq.c:2299
blk_mq_requeue_work+0x408/0x430 block/blk-mq.c:1484
process_one_work kernel/workqueue.c:3231 [inline]
process_scheduled_works+0x483/0x9a0 kernel/workqueue.c:3312
worker_thread+0x526/0x730 kernel/workqueue.c:3393
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

write to 0xffff888100e4f0f8 of 4 bytes by task 8963 on cpu 0:
blk_mq_dispatch_rq_list+0xd2d/0xf30
__blk_mq_do_dispatch_sched block/blk-mq-sched.c:170 [inline]
blk_mq_do_dispatch_sched block/blk-mq-sched.c:184 [inline]
__blk_mq_sched_dispatch_requests+0x604/0xd50 block/blk-mq-sched.c:309
blk_mq_sched_dispatch_requests+0x78/0xe0 block/blk-mq-sched.c:331
blk_mq_run_hw_queue+0x29c/0x4d0 block/blk-mq.c:2250
blk_mq_flush_plug_list+0x7bc/0xde0 block/blk-mq.c:2799
__blk_flush_plug+0x216/0x290 block/blk-core.c:1194
blk_finish_plug+0x48/0x70 block/blk-core.c:1221
wb_writeback+0x6d8/0x720 fs/fs-writeback.c:2165
wb_check_start_all fs/fs-writeback.c:2255 [inline]
wb_do_writeback fs/fs-writeback.c:2281 [inline]
wb_workfn+0x4ea/0x940 fs/fs-writeback.c:2314
process_one_work kernel/workqueue.c:3231 [inline]
process_scheduled_works+0x483/0x9a0 kernel/workqueue.c:3312
worker_thread+0x526/0x730 kernel/workqueue.c:3393
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

value changed: 0x00000001 -> 0x00000002

Reported by Kernel Concurrency Sanitizer on:
CPU: 0 PID: 8963 Comm: kworker/u8:16 Not tainted 6.10.0-rc4-syzkaller-00330-g7c16f0a4ed1c #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/07/2024
Workqueue: writeback wb_workfn (flush-8:0)
==================================================================


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