syzbot


WARNING in __blk_mq_delay_run_hw_queue

Status: fixed on 2020/05/10 10:41
Subsystems: block
[Documentation on labels]
Reported-by: syzbot+d44e1b26ce5c3e77458d@syzkaller.appspotmail.com
Fix commit: 6e66b4939241 blk-mq: Keep set->nr_hw_queues and set->map[].nr_queues in sync
First crash: 1716d, last: 1610d
Cause bisection: introduced by (bisect log) :
commit ed76e329d74a4b15ac0f5fd3adbd52ec0178a134
Author: Jens Axboe <axboe@kernel.dk>
Date: Mon Oct 29 19:06:14 2018 +0000

  blk-mq: abstract out queue map

Crash: WARNING in __blk_mq_delay_run_hw_queue (log)
Repro: C syz .config
  
Fix bisection: failed (error log, bisect log)
  
Discussions (12)
Title Replies (including bot) Last reply
[PATCH 5.6 00/38] 5.6.4-rc1 review 44 (44) 2020/04/14 10:36
[PATCH 5.5 00/44] 5.5.17-rc1 review 48 (48) 2020/04/14 10:36
[PATCH 5.4 00/41] 5.4.32-rc1 review 45 (45) 2020/04/14 10:36
[PATCH AUTOSEL 5.6 01/68] cpufreq: imx6q: Fixes unwanted cpu overclocking on i.MX6ULL 77 (77) 2020/04/13 17:19
[PATCH AUTOSEL 5.4 01/46] cpufreq: imx6q: Fixes unwanted cpu overclocking on i.MX6ULL 46 (46) 2020/04/10 03:49
[PATCH AUTOSEL 5.5 01/56] cpufreq: imx6q: Fixes unwanted cpu overclocking on i.MX6ULL 56 (56) 2020/04/10 03:48
[PATCH v4 0/8] Improve changing the number of hardware queues 10 (10) 2020/03/10 13:10
[PATCH v3 0/8] Improve changing the number of hardware queues 12 (12) 2020/03/06 10:04
Re: [PATCH v3 2/8] blk-mq: Keep set->nr_hw_queues and set->map[].nr_queues in sync 1 (1) 2020/02/24 11:00
[PATCH v2 0/8] Eight patches related to changing the number of hardware queues 13 (13) 2020/02/21 02:50
[PATCH 0/5] Five patches related to changing the number of hardware queues 10 (10) 2020/02/19 04:24
WARNING in __blk_mq_delay_run_hw_queue 0 (2) 2019/10/05 09:19

Sample crash report:
block nbd0: Dead connection, failed to find a fallback
block nbd0: shutting down sockets
blk_update_request: I/O error, dev nbd0, sector 2 op 0x0:(READ) flags 0x0 phys_seg 3 prio class 0
Buffer I/O error on dev nbd0, logical block 1, async page read
Buffer I/O error on dev nbd0, logical block 2, async page read
Buffer I/O error on dev nbd0, logical block 3, async page read
------------[ cut here ]------------
WARNING: CPU: 0 PID: 2501 at include/linux/cpumask.h:137 cpu_max_bits_warn include/linux/cpumask.h:137 [inline]
WARNING: CPU: 0 PID: 2501 at include/linux/cpumask.h:137 cpumask_check include/linux/cpumask.h:144 [inline]
WARNING: CPU: 0 PID: 2501 at include/linux/cpumask.h:137 cpumask_check include/linux/cpumask.h:142 [inline]
WARNING: CPU: 0 PID: 2501 at include/linux/cpumask.h:137 cpumask_test_cpu include/linux/cpumask.h:360 [inline]
WARNING: CPU: 0 PID: 2501 at include/linux/cpumask.h:137 blk_mq_hctx_next_cpu block/blk-mq.c:1443 [inline]
WARNING: CPU: 0 PID: 2501 at include/linux/cpumask.h:137 __blk_mq_delay_run_hw_queue+0x498/0x600 block/blk-mq.c:1479
Kernel panic - not syncing: panic_on_warn set ...
CPU: 0 PID: 2501 Comm: kworker/0:1H Not tainted 5.4.0-rc4 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Workqueue: kblockd blk_mq_requeue_work
Call Trace:
 __dump_stack lib/dump_stack.c:77 [inline]
 dump_stack+0x172/0x1f0 lib/dump_stack.c:113
 panic+0x2e3/0x75c kernel/panic.c:221
 __warn.cold+0x2f/0x35 kernel/panic.c:582
 report_bug+0x289/0x300 lib/bug.c:195
 fixup_bug arch/x86/kernel/traps.c:179 [inline]
 fixup_bug arch/x86/kernel/traps.c:174 [inline]
 do_error_trap+0x11b/0x200 arch/x86/kernel/traps.c:272
 do_invalid_op+0x37/0x50 arch/x86/kernel/traps.c:291
 invalid_op+0x23/0x30 arch/x86/entry/entry_64.S:1028
RIP: 0010:cpu_max_bits_warn include/linux/cpumask.h:137 [inline]
RIP: 0010:cpumask_check include/linux/cpumask.h:144 [inline]
RIP: 0010:cpumask_check include/linux/cpumask.h:142 [inline]
RIP: 0010:cpumask_test_cpu include/linux/cpumask.h:360 [inline]
RIP: 0010:blk_mq_hctx_next_cpu block/blk-mq.c:1443 [inline]
RIP: 0010:__blk_mq_delay_run_hw_queue+0x498/0x600 block/blk-mq.c:1479
Code: 01 00 00 41 c7 84 24 24 01 00 00 01 00 00 00 41 bd 40 00 00 00 e9 ab fe ff ff 41 bd 40 00 00 00 e9 a0 fe ff ff e8 28 16 40 fe <0f> 0b e9 50 fd ff ff e8 1c 16 40 fe 48 c7 c2 80 74 c6 89 4c 89 fe
RSP: 0018:ffff8880a2897b18 EFLAGS: 00010293
RAX: ffff8880a2882200 RBX: 0000000000000040 RCX: ffffffff8332fc66
RDX: 0000000000000000 RSI: ffffffff8332ff18 RDI: 0000000000000005
RBP: ffff8880a2897b58 R08: ffff8880a2882200 R09: ffffed1012f2100a
R10: ffffed1012f21009 R11: ffff88809790804f R12: ffff888097908000
R13: 0000000000000040 R14: ffff888097908124 R15: 0000000000000000
 blk_mq_run_hw_queue+0x19d/0x350 block/blk-mq.c:1508
 blk_mq_run_hw_queues+0x112/0x1a0 block/blk-mq.c:1525
 blk_mq_requeue_work+0x502/0x780 block/blk-mq.c:775
 process_one_work+0x9af/0x1740 kernel/workqueue.c:2269
 worker_thread+0x98/0xe40 kernel/workqueue.c:2415
 kthread+0x361/0x430 kernel/kthread.c:255
 ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:352
Kernel Offset: disabled
Rebooting in 86400 seconds..

Crashes (6):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2019/10/21 16:58 upstream 7d194c2100ad b24d2b8a .config console log report syz C ci-upstream-kasan-gce-selinux-root
2019/10/16 07:40 upstream 3b1f00aceb7a d4ea592f .config console log report syz C ci-upstream-kasan-gce-root
2019/10/05 03:16 upstream b145b0eb2031 f3f7d9c8 .config console log report syz C ci-upstream-kasan-gce-root
2020/01/18 07:59 upstream ab7541c3addd 3de7aabb .config console log report ci-upstream-kasan-gce-selinux-root
2019/10/05 06:51 upstream b145b0eb2031 f3f7d9c8 .config console log report ci-upstream-kasan-gce-root
2019/10/05 02:34 upstream b145b0eb2031 f3f7d9c8 .config console log report ci-upstream-kasan-gce-root
* Struck through repros no longer work on HEAD.