syzbot


KCSAN: data-race in lo_ioctl / loop_queue_rq (6)

Status: moderation: reported on 2025/10/26 10:53
Subsystems: block
[Documentation on labels]
Reported-by: syzbot+9e4925574d12b732f6a0@syzkaller.appspotmail.com
First crash: 59d, last: 51d
Similar bugs (5)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream KCSAN: data-race in lo_ioctl / loop_queue_rq (4) block 6 2 707d 722d 0/29 auto-obsoleted due to no activity on 2024/02/21 17:00
upstream KCSAN: data-race in lo_ioctl / loop_queue_rq (3) block 6 1 1257d 1257d 0/29 auto-closed as invalid on 2022/08/20 11:36
upstream KCSAN: data-race in lo_ioctl / loop_queue_rq (2) block 6 1 1703d 1703d 0/29 auto-closed as invalid on 2021/05/31 09:44
upstream KCSAN: data-race in lo_ioctl / loop_queue_rq (5) block 6 1 257d 257d 0/29 auto-obsoleted due to no activity on 2025/06/06 09:54
upstream KCSAN: data-race in lo_ioctl / loop_queue_rq block 6 1 2205d 2205d 0/29 auto-closed as invalid on 2020/02/19 07:26

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

write to 0xffff88810230d480 of 4 bytes by task 8982 on cpu 0:
 loop_clr_fd drivers/block/loop.c:1222 [inline]
 lo_ioctl+0xa66/0x12b0 drivers/block/loop.c:1549
 blkdev_ioctl+0x356/0x440 block/ioctl.c:705
 vfs_ioctl fs/ioctl.c:51 [inline]
 __do_sys_ioctl fs/ioctl.c:597 [inline]
 __se_sys_ioctl+0xce/0x140 fs/ioctl.c:583
 __x64_sys_ioctl+0x43/0x50 fs/ioctl.c:583
 x64_sys_call+0x1816/0x3000 arch/x86/include/generated/asm/syscalls_64.h:17
 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
 do_syscall_64+0xd2/0x200 arch/x86/entry/syscall_64.c:94
 entry_SYSCALL_64_after_hwframe+0x77/0x7f

read to 0xffff88810230d480 of 4 bytes by task 48 on cpu 1:
 loop_queue_rq+0x4f/0x680 drivers/block/loop.c:1862
 blk_mq_dispatch_rq_list+0x2a6/0xf80 block/blk-mq.c:2129
 __blk_mq_sched_dispatch_requests+0xb83/0xc60 block/blk-mq-sched.c:313
 blk_mq_sched_dispatch_requests+0x86/0x120 block/blk-mq-sched.c:329
 blk_mq_run_hw_queue+0x17e/0x220 block/blk-mq.c:2367
 blk_mq_run_hw_queues+0x180/0x250 block/blk-mq.c:2416
 blk_mq_requeue_work+0x3b9/0x3f0 block/blk-mq.c:1583
 process_one_work kernel/workqueue.c:3263 [inline]
 process_scheduled_works+0x4ce/0x9d0 kernel/workqueue.c:3346
 worker_thread+0x582/0x770 kernel/workqueue.c:3427
 kthread+0x489/0x510 kernel/kthread.c:463
 ret_from_fork+0x122/0x1b0 arch/x86/kernel/process.c:158
 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245

value changed: 0x00000001 -> 0x00000002

Reported by Kernel Concurrency Sanitizer on:
CPU: 1 UID: 0 PID: 48 Comm: kworker/1:1H Not tainted syzkaller #0 PREEMPT(voluntary) 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/02/2025
Workqueue: kblockd blk_mq_requeue_work
==================================================================
I/O error, dev loop5, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
Buffer I/O error on dev loop5, logical block 0, async page read

Crashes (2):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2025/11/03 09:53 upstream 6146a0f1dfae 2c50b6a9 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-kcsan-gce KCSAN: data-race in lo_ioctl / loop_queue_rq
2025/10/26 10:52 upstream 72761a7e3122 c0460fcd .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-kcsan-gce KCSAN: data-race in lo_ioctl / loop_queue_rq
* Struck through repros no longer work on HEAD.