syzbot


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

Status: auto-closed as invalid on 2022/01/25 22:50
Reported-by: syzbot+@syzkaller.appspotmail.com
First crash: 396d, last: 346d
similar bugs (7):
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream KCSAN: data-race in __blk_mq_sched_dispatch_requests / __blk_mq_sched_dispatch_requests (8) 1 198d 198d 0/24 auto-closed as invalid on 2022/06/22 21:22
upstream KCSAN: data-race in __blk_mq_sched_dispatch_requests / __blk_mq_sched_dispatch_requests (6) 1 491d 491d 0/24 auto-closed as invalid on 2021/09/03 00:46
upstream KCSAN: data-race in __blk_mq_sched_dispatch_requests / __blk_mq_sched_dispatch_requests (5) 1 527d 527d 0/24 auto-closed as invalid on 2021/07/29 00:14
upstream KCSAN: data-race in __blk_mq_sched_dispatch_requests / __blk_mq_sched_dispatch_requests 3 824d 855d 0/24 auto-closed as invalid on 2020/10/05 06:08
upstream KCSAN: data-race in __blk_mq_sched_dispatch_requests / __blk_mq_sched_dispatch_requests (3) 7 654d 726d 0/24 auto-closed as invalid on 2021/03/24 08:42
upstream KCSAN: data-race in __blk_mq_sched_dispatch_requests / __blk_mq_sched_dispatch_requests (4) 2 567d 614d 0/24 auto-closed as invalid on 2021/06/18 13:35
upstream KCSAN: data-race in __blk_mq_sched_dispatch_requests / __blk_mq_sched_dispatch_requests (2) 3 775d 783d 0/24 auto-closed as invalid on 2020/11/22 21:54

Sample crash report:
==================================================================
BUG: KCSAN: data-race in __blk_mq_sched_dispatch_requests / __blk_mq_sched_dispatch_requests

write to 0xffff888101d61410 of 8 bytes by task 24375 on cpu 1:
 INIT_LIST_HEAD include/linux/list.h:38 [inline]
 list_splice_init include/linux/list.h:485 [inline]
 __blk_mq_sched_dispatch_requests+0x137/0x270 block/blk-mq-sched.c:306
 blk_mq_sched_dispatch_requests+0x9f/0x110 block/blk-mq-sched.c:358
 __blk_mq_run_hw_queue+0xc1/0x140 block/blk-mq.c:1785
 __blk_mq_delay_run_hw_queue+0x199/0x360 block/blk-mq.c:1862
 blk_mq_run_hw_queue+0x231/0x260 block/blk-mq.c:1915
 blk_mq_sched_insert_request+0x117/0x220 block/blk-mq-sched.c:477
 blk_execute_rq_nowait+0x118/0x160 block/blk-exec.c:62
 sg_common_write+0x8d9/0x1480 drivers/scsi/sg.c:836
 sg_new_write+0xb32/0xcc0 drivers/scsi/sg.c:774
 sg_ioctl_common drivers/scsi/sg.c:939 [inline]
 sg_ioctl+0xee7/0x18e0 drivers/scsi/sg.c:1165
 vfs_ioctl fs/ioctl.c:51 [inline]
 __do_sys_ioctl fs/ioctl.c:874 [inline]
 __se_sys_ioctl+0xcb/0x140 fs/ioctl.c:860
 __x64_sys_ioctl+0x3f/0x50 fs/ioctl.c:860
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x44/0xd0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x44/0xae

read to 0xffff888101d61410 of 8 bytes by task 24376 on cpu 0:
 list_empty_careful include/linux/list.h:321 [inline]
 __blk_mq_sched_dispatch_requests+0x80/0x270 block/blk-mq-sched.c:303
 blk_mq_sched_dispatch_requests+0x9f/0x110 block/blk-mq-sched.c:358
 __blk_mq_run_hw_queue+0xc1/0x140 block/blk-mq.c:1785
 __blk_mq_delay_run_hw_queue+0x199/0x360 block/blk-mq.c:1862
 blk_mq_run_hw_queue+0x231/0x260 block/blk-mq.c:1915
 blk_mq_sched_insert_request+0x117/0x220 block/blk-mq-sched.c:477
 blk_execute_rq_nowait+0x118/0x160 block/blk-exec.c:62
 sg_common_write+0x8d9/0x1480 drivers/scsi/sg.c:836
 sg_new_write+0xb32/0xcc0 drivers/scsi/sg.c:774
 sg_ioctl_common drivers/scsi/sg.c:939 [inline]
 sg_ioctl+0xee7/0x18e0 drivers/scsi/sg.c:1165
 vfs_ioctl fs/ioctl.c:51 [inline]
 __do_sys_ioctl fs/ioctl.c:874 [inline]
 __se_sys_ioctl+0xcb/0x140 fs/ioctl.c:860
 __x64_sys_ioctl+0x3f/0x50 fs/ioctl.c:860
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x44/0xd0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x44/0xae

value changed: 0xffff888102a365c8 -> 0xffff888101d61408

Reported by Kernel Concurrency Sanitizer on:
CPU: 0 PID: 24376 Comm: syz-executor.1 Not tainted 5.16.0-rc6-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
==================================================================

Crashes (4):
Manager Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Title
ci2-upstream-kcsan-gce 2021/12/21 22:47 upstream 1c3e979bf3e2 6caa12e4 .config log report info KCSAN: data-race in __blk_mq_sched_dispatch_requests / __blk_mq_sched_dispatch_requests
ci2-upstream-kcsan-gce 2021/12/07 17:08 upstream cd8c917a56f2 0230ba3e .config log report info KCSAN: data-race in __blk_mq_sched_dispatch_requests / __blk_mq_sched_dispatch_requests
ci2-upstream-kcsan-gce 2021/11/30 10:02 upstream d58071a8a76d d0830353 .config log report info KCSAN: data-race in __blk_mq_sched_dispatch_requests / __blk_mq_sched_dispatch_requests
ci2-upstream-kcsan-gce 2021/11/01 23:47 upstream e66435936756 098b5d53 .config log report info KCSAN: data-race in __blk_mq_sched_dispatch_requests / __blk_mq_sched_dispatch_requests
* Struck through repros no longer work on HEAD.