syzbot


possible deadlock in blk_mq_update_nr_hw_queues

Status: upstream: reported C repro on 2024/11/24 23:13
Subsystems: block
[Documentation on labels]
Reported-by: syzbot+6279b273d888c2017726@syzkaller.appspotmail.com
First crash: 515d, last: 107d
Cause bisection: introduced by (bisect log) :
commit f1be1788a32e8fa63416ad4518bbd1a85a825c9d
Author: Ming Lei <ming.lei@redhat.com>
Date: Fri Oct 25 00:37:20 2024 +0000

  block: model freeze & enter queue as lock for supporting lockdep

Crash: BUG: MAX_LOCKDEP_KEYS too low! (log)
Repro: C syz .config
  
Fix bisection: failed (error log, bisect log)
  
Discussions (6)
Title Replies (including bot) Last reply
[syzbot] Monthly block report (Sep 2025) 0 (1) 2025/09/27 20:43
[syzbot] Monthly block report (Aug 2025) 0 (1) 2025/08/27 08:15
[syzbot] Monthly block report (Jul 2025) 0 (1) 2025/07/27 10:41
[syzbot] [block?] possible deadlock in blk_mq_update_nr_hw_queues 0 (3) 2025/07/13 12:20
[syzbot] Monthly block report (Jun 2025) 0 (1) 2025/06/26 05:36
[syzbot] Monthly block report (Apr 2025) 0 (1) 2025/04/24 13:06
Last patch testing requests (6)
Created Duration User Patch Repo Result
2026/04/13 06:22 23m retest repro net-next report log
2026/04/06 10:21 19m retest repro upstream OK log
2026/01/26 09:39 13m retest repro upstream report log
2025/11/17 08:46 14m retest repro upstream report log
2025/09/06 20:19 1h15m retest repro net-next report log
2025/09/06 15:54 13m retest repro upstream report log
Fix bisection attempts (5)
Created Duration User Patch Repo Result
2026/02/02 05:43 28m bisect fix net-next error job log
2026/01/03 03:08 2h30m bisect fix net-next OK (0) job log log
2025/12/04 00:44 2h23m bisect fix net-next OK (0) job log log
2025/11/03 06:22 2h04m bisect fix net-next OK (0) job log log
2025/09/26 22:16 3h03m bisect fix net-next OK (0) job log log

Sample crash report:
======================================================
WARNING: possible circular locking dependency detected
6.16.0-rc5-syzkaller-01399-ga52f9f0d77f2 #0 Not tainted
------------------------------------------------------
syz-executor137/5864 is trying to acquire lock:
ffff8880254af988 (&set->update_nr_hwq_lock){++++}-{4:4}, at: blk_mq_update_nr_hw_queues+0x3b/0x14c0 block/blk-mq.c:5041

but task is already holding lock:
ffff8880254afa30 (&nbd->config_lock){+.+.}-{4:4}, at: nbd_genl_connect+0x94f/0x1930 drivers/block/nbd.c:2111

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #2 (&nbd->config_lock){+.+.}-{4:4}:
       lock_acquire+0x120/0x360 kernel/locking/lockdep.c:5871
       __mutex_lock_common kernel/locking/mutex.c:602 [inline]
       __mutex_lock+0x182/0xe80 kernel/locking/mutex.c:747
       refcount_dec_and_mutex_lock+0x30/0xa0 lib/refcount.c:118
       nbd_config_put+0x2c/0x790 drivers/block/nbd.c:1423
       nbd_release+0xfe/0x140 drivers/block/nbd.c:1735
       bdev_release+0x536/0x650 block/bdev.c:-1
       blkdev_release+0x15/0x20 block/fops.c:684
       __fput+0x449/0xa70 fs/file_table.c:465
       fput_close_sync+0x119/0x200 fs/file_table.c:570
       __do_sys_close fs/open.c:1589 [inline]
       __se_sys_close fs/open.c:1574 [inline]
       __x64_sys_close+0x7f/0x110 fs/open.c:1574
       do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
       do_syscall_64+0xfa/0x3b0 arch/x86/entry/syscall_64.c:94
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

-> #1 (&disk->open_mutex){+.+.}-{4:4}:
       lock_acquire+0x120/0x360 kernel/locking/lockdep.c:5871
       __mutex_lock_common kernel/locking/mutex.c:602 [inline]
       __mutex_lock+0x182/0xe80 kernel/locking/mutex.c:747
       __del_gendisk+0x129/0x9e0 block/genhd.c:710
       del_gendisk+0xe8/0x160 block/genhd.c:823
       nbd_dev_remove drivers/block/nbd.c:268 [inline]
       nbd_dev_remove_work+0x47/0xe0 drivers/block/nbd.c:284
       process_one_work kernel/workqueue.c:3238 [inline]
       process_scheduled_works+0xae1/0x17b0 kernel/workqueue.c:3321
       worker_thread+0x8a0/0xda0 kernel/workqueue.c:3402
       kthread+0x70e/0x8a0 kernel/kthread.c:464
       ret_from_fork+0x3fc/0x770 arch/x86/kernel/process.c:148
       ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245

-> #0 (&set->update_nr_hwq_lock){++++}-{4:4}:
       check_prev_add kernel/locking/lockdep.c:3168 [inline]
       check_prevs_add kernel/locking/lockdep.c:3287 [inline]
       validate_chain+0xb9b/0x2140 kernel/locking/lockdep.c:3911
       __lock_acquire+0xab9/0xd20 kernel/locking/lockdep.c:5240
       lock_acquire+0x120/0x360 kernel/locking/lockdep.c:5871
       down_write+0x96/0x1f0 kernel/locking/rwsem.c:1577
       blk_mq_update_nr_hw_queues+0x3b/0x14c0 block/blk-mq.c:5041
       nbd_start_device+0x16c/0xac0 drivers/block/nbd.c:1476
       nbd_genl_connect+0x1250/0x1930 drivers/block/nbd.c:2201
       genl_family_rcv_msg_doit+0x215/0x300 net/netlink/genetlink.c:1115
       genl_family_rcv_msg net/netlink/genetlink.c:1195 [inline]
       genl_rcv_msg+0x60e/0x790 net/netlink/genetlink.c:1210
       netlink_rcv_skb+0x205/0x470 net/netlink/af_netlink.c:2552
       genl_rcv+0x28/0x40 net/netlink/genetlink.c:1219
       netlink_unicast_kernel net/netlink/af_netlink.c:1320 [inline]
       netlink_unicast+0x75c/0x8e0 net/netlink/af_netlink.c:1346
       netlink_sendmsg+0x805/0xb30 net/netlink/af_netlink.c:1896
       sock_sendmsg_nosec net/socket.c:714 [inline]
       __sock_sendmsg+0x219/0x270 net/socket.c:729
       ____sys_sendmsg+0x505/0x830 net/socket.c:2614
       ___sys_sendmsg+0x21f/0x2a0 net/socket.c:2668
       __sys_sendmsg net/socket.c:2700 [inline]
       __do_sys_sendmsg net/socket.c:2705 [inline]
       __se_sys_sendmsg net/socket.c:2703 [inline]
       __x64_sys_sendmsg+0x19b/0x260 net/socket.c:2703
       do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
       do_syscall_64+0xfa/0x3b0 arch/x86/entry/syscall_64.c:94
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

other info that might help us debug this:

Chain exists of:
  &set->update_nr_hwq_lock --> &disk->open_mutex --> &nbd->config_lock

 Possible unsafe locking scenario:

       CPU0                    CPU1
       ----                    ----
  lock(&nbd->config_lock);
                               lock(&disk->open_mutex);
                               lock(&nbd->config_lock);
  lock(&set->update_nr_hwq_lock);

 *** DEADLOCK ***

3 locks held by syz-executor137/5864:
 #0: ffffffff8f5854b0 (cb_lock){++++}-{4:4}, at: genl_rcv+0x19/0x40 net/netlink/genetlink.c:1218
 #1: ffffffff8f5852c8 (genl_mutex){+.+.}-{4:4}, at: genl_lock net/netlink/genetlink.c:35 [inline]
 #1: ffffffff8f5852c8 (genl_mutex){+.+.}-{4:4}, at: genl_op_lock net/netlink/genetlink.c:60 [inline]
 #1: ffffffff8f5852c8 (genl_mutex){+.+.}-{4:4}, at: genl_rcv_msg+0x10d/0x790 net/netlink/genetlink.c:1209
 #2: ffff8880254afa30 (&nbd->config_lock){+.+.}-{4:4}, at: nbd_genl_connect+0x94f/0x1930 drivers/block/nbd.c:2111

stack backtrace:
CPU: 1 UID: 0 PID: 5864 Comm: syz-executor137 Not tainted 6.16.0-rc5-syzkaller-01399-ga52f9f0d77f2 #0 PREEMPT(full) 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025
Call Trace:
 <TASK>
 dump_stack_lvl+0x189/0x250 lib/dump_stack.c:120
 print_circular_bug+0x2ee/0x310 kernel/locking/lockdep.c:2046
 check_noncircular+0x134/0x160 kernel/locking/lockdep.c:2178
 check_prev_add kernel/locking/lockdep.c:3168 [inline]
 check_prevs_add kernel/locking/lockdep.c:3287 [inline]
 validate_chain+0xb9b/0x2140 kernel/locking/lockdep.c:3911
 __lock_acquire+0xab9/0xd20 kernel/locking/lockdep.c:5240
 lock_acquire+0x120/0x360 kernel/locking/lockdep.c:5871
 down_write+0x96/0x1f0 kernel/locking/rwsem.c:1577
 blk_mq_update_nr_hw_queues+0x3b/0x14c0 block/blk-mq.c:5041
 nbd_start_device+0x16c/0xac0 drivers/block/nbd.c:1476
 nbd_genl_connect+0x1250/0x1930 drivers/block/nbd.c:2201
 genl_family_rcv_msg_doit+0x215/0x300 net/netlink/genetlink.c:1115
 genl_family_rcv_msg net/netlink/genetlink.c:1195 [inline]
 genl_rcv_msg+0x60e/0x790 net/netlink/genetlink.c:1210
 netlink_rcv_skb+0x205/0x470 net/netlink/af_netlink.c:2552
 genl_rcv+0x28/0x40 net/netlink/genetlink.c:1219
 netlink_unicast_kernel net/netlink/af_netlink.c:1320 [inline]
 netlink_unicast+0x75c/0x8e0 net/netlink/af_netlink.c:1346
 netlink_sendmsg+0x805/0xb30 net/netlink/af_netlink.c:1896
 sock_sendmsg_nosec net/socket.c:714 [inline]
 __sock_sendmsg+0x219/0x270 net/socket.c:729
 ____sys_sendmsg+0x505/0x830 net/socket.c:2614
 ___sys_sendmsg+0x21f/0x2a0 net/socket.c:2668
 __sys_sendmsg net/socket.c:2700 [inline]
 __do_sys_sendmsg net/socket.c:2705 [inline]
 __se_sys_sendmsg net/socket.c:2703 [inline]
 __x64_sys_sendmsg+0x19b/0x260 net/socket.c:2703
 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
 do_syscall_64+0xfa/0x3b0 arch/x86/entry/syscall_64.c:94
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f8697943ad9
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 71 19 00 00 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ffe0f0edd68 EFLAGS: 00000246 ORIG_RAX: 000000000000002e
RAX: ffffffffffffffda RBX: 00002000000004c0 RCX: 00007f8697943ad9
RDX: 0000000020000000 RSI: 0000200000001ac0 RDI: 0000000000000004
RBP: 0000000000000000 R08: 0000000000000006 R09: 0000000000000006
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000003a28
R13: 431bde82d7b634db R14: 0000000000000001 R15: 0000000000000001
 </TASK>
nbd0: detected capacity change from 0 to 127

Crashes (44250):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2025/07/12 23:57 net-next a52f9f0d77f2 3cda49cf .config strace log report syz / log C [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in blk_mq_update_nr_hw_queues
2025/08/23 15:10 upstream 038d61fd6422 bf27483f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in blk_mq_update_nr_hw_queues
2025/08/23 14:03 upstream 038d61fd6422 bf27483f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in blk_mq_update_nr_hw_queues
2025/08/23 12:51 upstream 038d61fd6422 bf27483f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in blk_mq_update_nr_hw_queues
2025/08/23 10:50 upstream 038d61fd6422 bf27483f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in blk_mq_update_nr_hw_queues
2025/08/23 10:30 upstream 038d61fd6422 bf27483f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in blk_mq_update_nr_hw_queues
2025/08/23 09:21 upstream 038d61fd6422 bf27483f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in blk_mq_update_nr_hw_queues
2025/08/23 07:43 upstream 038d61fd6422 bf27483f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in blk_mq_update_nr_hw_queues
2025/08/23 06:25 upstream 038d61fd6422 bf27483f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in blk_mq_update_nr_hw_queues
2025/08/23 04:27 upstream 038d61fd6422 bf27483f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in blk_mq_update_nr_hw_queues
2025/08/23 02:24 upstream 038d61fd6422 bf27483f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in blk_mq_update_nr_hw_queues
2025/08/23 00:06 upstream 038d61fd6422 bf27483f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in blk_mq_update_nr_hw_queues
2025/08/22 22:17 upstream 038d61fd6422 bf27483f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in blk_mq_update_nr_hw_queues
2025/08/22 18:15 upstream 038d61fd6422 bf27483f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in blk_mq_update_nr_hw_queues
2025/08/22 17:05 upstream 038d61fd6422 bf27483f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in blk_mq_update_nr_hw_queues
2025/08/22 15:05 upstream 038d61fd6422 bf27483f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in blk_mq_update_nr_hw_queues
2025/08/22 07:29 upstream 038d61fd6422 bf27483f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in blk_mq_update_nr_hw_queues
2025/08/22 06:03 upstream 038d61fd6422 bf27483f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in blk_mq_update_nr_hw_queues
2025/08/22 03:45 upstream 038d61fd6422 bf27483f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in blk_mq_update_nr_hw_queues
2025/08/22 01:50 upstream 038d61fd6422 bf27483f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in blk_mq_update_nr_hw_queues
2025/08/21 23:51 upstream 038d61fd6422 bf27483f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in blk_mq_update_nr_hw_queues
2025/08/21 17:12 upstream 038d61fd6422 0b9605c8 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in blk_mq_update_nr_hw_queues
2025/08/21 15:54 upstream 038d61fd6422 0b9605c8 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in blk_mq_update_nr_hw_queues
2025/08/21 14:51 upstream 038d61fd6422 0b9605c8 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in blk_mq_update_nr_hw_queues
2025/08/21 13:32 upstream 038d61fd6422 0b9605c8 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in blk_mq_update_nr_hw_queues
2025/08/21 09:53 upstream 038d61fd6422 0b9605c8 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in blk_mq_update_nr_hw_queues
2025/08/21 06:03 upstream 038d61fd6422 0b9605c8 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in blk_mq_update_nr_hw_queues
2025/08/21 04:49 upstream 038d61fd6422 0b9605c8 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in blk_mq_update_nr_hw_queues
2025/08/21 03:34 upstream 038d61fd6422 0b9605c8 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in blk_mq_update_nr_hw_queues
2025/08/21 01:48 upstream 038d61fd6422 0b9605c8 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in blk_mq_update_nr_hw_queues
2025/08/20 23:21 upstream 038d61fd6422 bd178e57 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in blk_mq_update_nr_hw_queues
2025/08/20 18:25 upstream 038d61fd6422 bd178e57 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in blk_mq_update_nr_hw_queues
2025/08/20 17:06 upstream 038d61fd6422 bd178e57 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in blk_mq_update_nr_hw_queues
2025/08/20 16:05 upstream 038d61fd6422 bd178e57 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in blk_mq_update_nr_hw_queues
2025/08/20 14:41 upstream 038d61fd6422 bd178e57 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in blk_mq_update_nr_hw_queues
2025/08/20 13:10 upstream 038d61fd6422 bd178e57 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in blk_mq_update_nr_hw_queues
2025/08/20 09:16 upstream 038d61fd6422 79512909 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in blk_mq_update_nr_hw_queues
2025/08/20 03:30 upstream 038d61fd6422 79512909 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in blk_mq_update_nr_hw_queues
2025/08/20 02:00 upstream 038d61fd6422 79512909 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in blk_mq_update_nr_hw_queues
2025/08/20 00:43 upstream 038d61fd6422 79512909 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in blk_mq_update_nr_hw_queues
2025/08/20 00:11 upstream 038d61fd6422 79512909 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in blk_mq_update_nr_hw_queues
2025/08/19 22:34 upstream 038d61fd6422 79512909 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in blk_mq_update_nr_hw_queues
2025/08/19 21:11 upstream 038d61fd6422 523f460e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in blk_mq_update_nr_hw_queues
2025/08/19 19:19 upstream 038d61fd6422 523f460e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in blk_mq_update_nr_hw_queues
2025/08/19 16:50 upstream 038d61fd6422 523f460e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in blk_mq_update_nr_hw_queues
2025/08/19 13:44 upstream 038d61fd6422 523f460e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in blk_mq_update_nr_hw_queues
2025/07/29 00:53 upstream 038d61fd6422 c4a95487 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in blk_mq_update_nr_hw_queues
2025/07/28 18:37 upstream 038d61fd6422 c4a95487 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-badwrites-root possible deadlock in blk_mq_update_nr_hw_queues
2025/07/28 07:29 upstream b711733e89a3 fb8f743d .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in blk_mq_update_nr_hw_queues
2025/07/26 21:04 upstream 302f88ff3584 fb8f743d .config console log report info [disk image] [vmlinux] [kernel image] ci-qemu-gce-upstream-auto possible deadlock in blk_mq_update_nr_hw_queues
2024/11/23 02:44 upstream 06afb0f36106 68da6d95 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in blk_mq_update_nr_hw_queues
2024/11/20 23:08 upstream bf9aa14fc523 4fca1650 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in blk_mq_update_nr_hw_queues
2025/07/28 11:59 upstream 038d61fd6422 fb8f743d .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in blk_mq_update_nr_hw_queues
2025/07/18 06:22 upstream 6832a9317eee 88248e14 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in blk_mq_update_nr_hw_queues
2025/04/03 19:35 upstream a2cc6ff5ec8f d7ae3a11 .config console log report syz / log C [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in blk_mq_update_nr_hw_queues
2025/07/28 21:10 upstream 038d61fd6422 032c6886 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in blk_mq_update_nr_hw_queues
2025/07/13 15:45 upstream 3f31a806a62e 3cda49cf .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu2-arm64 possible deadlock in blk_mq_update_nr_hw_queues
2025/06/10 06:42 upstream 19272b37aa4f 4826c28e .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu2-arm64-compat possible deadlock in blk_mq_update_nr_hw_queues
2025/07/30 20:02 net afd8c2c9e2e2 f8f2b4da .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce possible deadlock in blk_mq_update_nr_hw_queues
2025/07/30 18:30 net-next fa582ca7e187 f8f2b4da .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in blk_mq_update_nr_hw_queues
2025/07/10 07:28 linux-next 835244aba90d 956bd956 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in blk_mq_update_nr_hw_queues
2025/07/09 12:54 linux-next 58ba80c47402 abade794 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-rust-kasan-gce possible deadlock in blk_mq_update_nr_hw_queues
2025/08/11 10:21 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 82af5ea7c611 32a0e5ed .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in blk_mq_update_nr_hw_queues
2025/08/06 17:22 git://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux.git for-next fda589c28604 4bd24a3e .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu2-riscv64 possible deadlock in blk_mq_update_nr_hw_queues
* Struck through repros no longer work on HEAD.