syzbot


KCSAN: data-race in blk_mq_dispatch_rq_list / blk_mq_dispatch_rq_list (7)

Status: auto-obsoleted due to no activity on 2024/07/29 01:45
Subsystems: block
[Documentation on labels]
Reported-by: syzbot+cd59997629d2514141ae@syzkaller.appspotmail.com
First crash: 104d, last: 104d
Similar bugs (6)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream KCSAN: data-race in blk_mq_dispatch_rq_list / blk_mq_dispatch_rq_list (4) block 2 935d 937d 0/28 auto-closed as invalid on 2022/04/19 11:06
upstream KCSAN: data-race in blk_mq_dispatch_rq_list / blk_mq_dispatch_rq_list (6) block 1 160d 160d 0/28 auto-obsoleted due to no activity on 2024/06/03 04:17
upstream KCSAN: data-race in blk_mq_dispatch_rq_list / blk_mq_dispatch_rq_list (3) block 1 983d 983d 0/28 auto-closed as invalid on 2022/03/02 19:51
upstream KCSAN: data-race in blk_mq_dispatch_rq_list / blk_mq_dispatch_rq_list block 2 1822d 1823d 0/28 closed as invalid on 2019/10/18 14:11
upstream KCSAN: data-race in blk_mq_dispatch_rq_list / blk_mq_dispatch_rq_list (2) block 1741 1070d 1766d 0/28 auto-closed as invalid on 2021/12/06 01:22
upstream KCSAN: data-race in blk_mq_dispatch_rq_list / blk_mq_dispatch_rq_list (5) block 168 196d 303d 0/28 auto-obsoleted due to no activity on 2024/04/27 14:29

Sample crash report:
==================================================================
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)
==================================================================

Crashes (1):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2024/06/24 01:45 upstream 7c16f0a4ed1c edc5149a .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-kcsan-gce KCSAN: data-race in blk_mq_dispatch_rq_list / blk_mq_dispatch_rq_list
* Struck through repros no longer work on HEAD.