syzbot


possible deadlock in pcpu_alloc_noprof (2)

Status: upstream: reported C repro on 2025/06/14 17:27
Subsystems: nbd
[Documentation on labels]
Reported-by: syzbot+91771b3fb86ec2dd7227@syzkaller.appspotmail.com
First crash: 120d, last: 12h44m
Discussions (4)
Title Replies (including bot) Last reply
[syzbot] Monthly nbd report (Oct 2025) 0 (1) 2025/10/06 17:29
[syzbot] Monthly nbd report (Sep 2025) 0 (1) 2025/09/03 12:36
[syzbot] Monthly block report (Jun 2025) 0 (1) 2025/06/26 05:36
[syzbot] [block?] possible deadlock in pcpu_alloc_noprof (2) 0 (1) 2025/06/14 17:27
Similar bugs (1)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream possible deadlock in pcpu_alloc_noprof block 4 C 257 120d 374d 28/29 fixed on 2025/06/10 16:19

Sample crash report:
======================================================
WARNING: possible circular locking dependency detected
syzkaller #0 Not tainted
------------------------------------------------------
syz.0.17/6137 is trying to acquire lock:
ffffffff8e728d48 (pcpu_alloc_mutex){+.+.}-{4:4}, at: pcpu_alloc_noprof+0xb4c/0x14c0 mm/percpu.c:1782

but task is already holding lock:
ffff888027963b88 (&q->q_usage_counter(io)#49){++++}-{0:0}, at: blk_mq_freeze_queue_nomemsave block/blk-mq.c:205 [inline]
ffff888027963b88 (&q->q_usage_counter(io)#49){++++}-{0:0}, at: __blk_mq_update_nr_hw_queues+0x899/0x1200 block/blk-mq.c:5070

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #2 (&q->q_usage_counter(io)#49){++++}-{0:0}:
       blk_alloc_queue+0x619/0x760 block/blk-core.c:461
       blk_mq_alloc_queue+0x172/0x280 block/blk-mq.c:4400
       __blk_mq_alloc_disk+0x29/0x120 block/blk-mq.c:4447
       nbd_dev_add+0x492/0xbb0 drivers/block/nbd.c:1943
       nbd_init+0x181/0x320 drivers/block/nbd.c:2680
       do_one_initcall+0x120/0x6e0 init/main.c:1269
       do_initcall_level init/main.c:1331 [inline]
       do_initcalls init/main.c:1347 [inline]
       do_basic_setup init/main.c:1366 [inline]
       kernel_init_freeable+0x5c2/0x910 init/main.c:1579
       kernel_init+0x1c/0x2b0 init/main.c:1469
       ret_from_fork+0x56a/0x730 arch/x86/kernel/process.c:148
       ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245

-> #1 (fs_reclaim){+.+.}-{0:0}:
       __fs_reclaim_acquire mm/page_alloc.c:4234 [inline]
       fs_reclaim_acquire+0x102/0x150 mm/page_alloc.c:4248
       might_alloc include/linux/sched/mm.h:318 [inline]
       prepare_alloc_pages+0x162/0x610 mm/page_alloc.c:4916
       __alloc_frozen_pages_noprof+0x18b/0x23f0 mm/page_alloc.c:5137
       __alloc_pages_noprof+0xb/0x1b0 mm/page_alloc.c:5182
       __alloc_pages_node_noprof include/linux/gfp.h:284 [inline]
       alloc_pages_node_noprof include/linux/gfp.h:311 [inline]
       pcpu_alloc_pages mm/percpu-vm.c:95 [inline]
       pcpu_populate_chunk+0x110/0xb00 mm/percpu-vm.c:285
       pcpu_alloc_noprof+0x86a/0x14c0 mm/percpu.c:1870
       iommu_dma_init_fq_percpu drivers/iommu/dma-iommu.c:320 [inline]
       iommu_dma_init_fq+0x202/0x8a0 drivers/iommu/dma-iommu.c:346
       iommu_dma_init_domain drivers/iommu/dma-iommu.c:709 [inline]
       iommu_setup_dma_ops+0x1336/0x1700 drivers/iommu/dma-iommu.c:2106
       bus_iommu_probe+0x23e/0x530 drivers/iommu/iommu.c:1911
       iommu_device_register+0x1af/0x280 drivers/iommu/iommu.c:277
       intel_iommu_init+0x25e7/0x3780 drivers/iommu/intel/iommu.c:3136
       pci_iommu_init+0x2e/0x90 arch/x86/kernel/pci-dma.c:174
       do_one_initcall+0x120/0x6e0 init/main.c:1269
       do_initcall_level init/main.c:1331 [inline]
       do_initcalls init/main.c:1347 [inline]
       do_basic_setup init/main.c:1366 [inline]
       kernel_init_freeable+0x5c2/0x910 init/main.c:1579
       kernel_init+0x1c/0x2b0 init/main.c:1469
       ret_from_fork+0x56a/0x730 arch/x86/kernel/process.c:148
       ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245

-> #0 (pcpu_alloc_mutex){+.+.}-{4:4}:
       check_prev_add kernel/locking/lockdep.c:3165 [inline]
       check_prevs_add kernel/locking/lockdep.c:3284 [inline]
       validate_chain kernel/locking/lockdep.c:3908 [inline]
       __lock_acquire+0x12a6/0x1ce0 kernel/locking/lockdep.c:5237
       lock_acquire kernel/locking/lockdep.c:5868 [inline]
       lock_acquire+0x179/0x350 kernel/locking/lockdep.c:5825
       __mutex_lock_common kernel/locking/mutex.c:598 [inline]
       __mutex_lock+0x193/0x1060 kernel/locking/mutex.c:760
       pcpu_alloc_noprof+0xb4c/0x14c0 mm/percpu.c:1782
       init_alloc_hint lib/sbitmap.c:16 [inline]
       sbitmap_init_node+0x2fd/0x770 lib/sbitmap.c:126
       sbitmap_queue_init_node+0x40/0x4a0 lib/sbitmap.c:454
       bt_alloc block/blk-mq-tag.c:542 [inline]
       blk_mq_init_tags+0x12d/0x2b0 block/blk-mq-tag.c:565
       blk_mq_alloc_rq_map block/blk-mq.c:3542 [inline]
       blk_mq_alloc_map_and_rqs+0x237/0xf60 block/blk-mq.c:4098
       __blk_mq_alloc_map_and_rqs block/blk-mq.c:4120 [inline]
       __blk_mq_alloc_map_and_rqs+0x128/0x1f0 block/blk-mq.c:4111
       blk_mq_realloc_tag_set_tags block/blk-mq.c:4759 [inline]
       __blk_mq_update_nr_hw_queues+0xcc1/0x1200 block/blk-mq.c:5072
       blk_mq_update_nr_hw_queues+0x3b/0x60 block/blk-mq.c:5124
       nbd_start_device+0x1b0/0xd70 drivers/block/nbd.c:1478
       nbd_start_device_ioctl drivers/block/nbd.c:1537 [inline]
       __nbd_ioctl drivers/block/nbd.c:1612 [inline]
       nbd_ioctl+0x219/0xda0 drivers/block/nbd.c:1652
       blkdev_ioctl+0x274/0x6d0 block/ioctl.c:705
       vfs_ioctl fs/ioctl.c:51 [inline]
       __do_sys_ioctl fs/ioctl.c:598 [inline]
       __se_sys_ioctl fs/ioctl.c:584 [inline]
       __x64_sys_ioctl+0x18b/0x210 fs/ioctl.c:584
       do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
       do_syscall_64+0xcd/0x4e0 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:
  pcpu_alloc_mutex --> fs_reclaim --> &q->q_usage_counter(io)#49

 Possible unsafe locking scenario:

       CPU0                    CPU1
       ----                    ----
  lock(&q->q_usage_counter(io)#49);
                               lock(fs_reclaim);
                               lock(&q->q_usage_counter(io)#49);
  lock(pcpu_alloc_mutex);

 *** DEADLOCK ***

4 locks held by syz.0.17/6137:
 #0: ffff888027a2f188 (&set->update_nr_hwq_lock){++++}-{4:4}, at: blk_mq_update_nr_hw_queues+0x27/0x60 block/blk-mq.c:5122
 #1: ffff888027a2f0d8 (&set->tag_list_lock){+.+.}-{4:4}, at: blk_mq_update_nr_hw_queues+0x31/0x60 block/blk-mq.c:5123
 #2: ffff888027963b88 (&q->q_usage_counter(io)#49){++++}-{0:0}, at: blk_mq_freeze_queue_nomemsave block/blk-mq.c:205 [inline]
 #2: ffff888027963b88 (&q->q_usage_counter(io)#49){++++}-{0:0}, at: __blk_mq_update_nr_hw_queues+0x899/0x1200 block/blk-mq.c:5070
 #3: ffff888027963bc0 (&q->q_usage_counter(queue)#33){+.+.}-{0:0}, at: blk_mq_freeze_queue_nomemsave block/blk-mq.c:205 [inline]
 #3: ffff888027963bc0 (&q->q_usage_counter(queue)#33){+.+.}-{0:0}, at: __blk_mq_update_nr_hw_queues+0x899/0x1200 block/blk-mq.c:5070

stack backtrace:
CPU: 1 UID: 0 PID: 6137 Comm: syz.0.17 Not tainted syzkaller #0 PREEMPT(full) 
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:94 [inline]
 dump_stack_lvl+0x116/0x1f0 lib/dump_stack.c:120
 print_circular_bug+0x275/0x350 kernel/locking/lockdep.c:2043
 check_noncircular+0x14c/0x170 kernel/locking/lockdep.c:2175
 check_prev_add kernel/locking/lockdep.c:3165 [inline]
 check_prevs_add kernel/locking/lockdep.c:3284 [inline]
 validate_chain kernel/locking/lockdep.c:3908 [inline]
 __lock_acquire+0x12a6/0x1ce0 kernel/locking/lockdep.c:5237
 lock_acquire kernel/locking/lockdep.c:5868 [inline]
 lock_acquire+0x179/0x350 kernel/locking/lockdep.c:5825
 __mutex_lock_common kernel/locking/mutex.c:598 [inline]
 __mutex_lock+0x193/0x1060 kernel/locking/mutex.c:760
 pcpu_alloc_noprof+0xb4c/0x14c0 mm/percpu.c:1782
 init_alloc_hint lib/sbitmap.c:16 [inline]
 sbitmap_init_node+0x2fd/0x770 lib/sbitmap.c:126
 sbitmap_queue_init_node+0x40/0x4a0 lib/sbitmap.c:454
 bt_alloc block/blk-mq-tag.c:542 [inline]
 blk_mq_init_tags+0x12d/0x2b0 block/blk-mq-tag.c:565
 blk_mq_alloc_rq_map block/blk-mq.c:3542 [inline]
 blk_mq_alloc_map_and_rqs+0x237/0xf60 block/blk-mq.c:4098
 __blk_mq_alloc_map_and_rqs block/blk-mq.c:4120 [inline]
 __blk_mq_alloc_map_and_rqs+0x128/0x1f0 block/blk-mq.c:4111
 blk_mq_realloc_tag_set_tags block/blk-mq.c:4759 [inline]
 __blk_mq_update_nr_hw_queues+0xcc1/0x1200 block/blk-mq.c:5072
 blk_mq_update_nr_hw_queues+0x3b/0x60 block/blk-mq.c:5124
 nbd_start_device+0x1b0/0xd70 drivers/block/nbd.c:1478
 nbd_start_device_ioctl drivers/block/nbd.c:1537 [inline]
 __nbd_ioctl drivers/block/nbd.c:1612 [inline]
 nbd_ioctl+0x219/0xda0 drivers/block/nbd.c:1652
 blkdev_ioctl+0x274/0x6d0 block/ioctl.c:705
 vfs_ioctl fs/ioctl.c:51 [inline]
 __do_sys_ioctl fs/ioctl.c:598 [inline]
 __se_sys_ioctl fs/ioctl.c:584 [inline]
 __x64_sys_ioctl+0x18b/0x210 fs/ioctl.c:584
 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
 do_syscall_64+0xcd/0x4e0 arch/x86/entry/syscall_64.c:94
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7faa9358eec9
Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 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 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ffc92f25af8 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007faa937e5fa0 RCX: 00007faa9358eec9
RDX: 0000000000000000 RSI: 000000000000ab03 RDI: 0000000000000003
RBP: 00007faa93611f91 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007faa937e5fa0 R14: 00007faa937e5fa0 R15: 0000000000000002
 </TASK>
block nbd0: shutting down sockets

Crashes (2189):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2025/09/25 13:26 upstream bf40f4b87761 0abd0691 .config console log report syz / log C [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in pcpu_alloc_noprof
2025/06/10 22:02 upstream f09079bd04a9 5d7e17ca .config console log report syz / log C [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in pcpu_alloc_noprof
2025/07/02 18:25 linux-next 50c8770a42fa 0cd59a8f .config strace log report syz / log C [disk image] [vmlinux] [kernel image] ci-upstream-rust-kasan-gce possible deadlock in pcpu_alloc_noprof
2025/10/05 14:52 linux-next 47a8d4b89844 49379ee0 .config console log report syz / log [disk image] [vmlinux] [kernel image] ci-upstream-rust-kasan-gce possible deadlock in pcpu_alloc_noprof
2025/10/08 12:01 upstream 971199ad2a0f 7e2882b3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in pcpu_alloc_noprof
2025/10/07 07:05 upstream c746c3b51698 8ef35d49 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-badwrites-root possible deadlock in pcpu_alloc_noprof
2025/10/07 01:44 upstream fd94619c4336 91305dbe .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in pcpu_alloc_noprof
2025/10/06 23:40 upstream fd94619c4336 91305dbe .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in pcpu_alloc_noprof
2025/10/06 01:41 upstream 6093a688a07d 49379ee0 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in pcpu_alloc_noprof
2025/09/15 03:09 upstream 79e8447ec662 e2beed91 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in pcpu_alloc_noprof
2025/08/08 17:52 upstream bec077162bd0 56444e07 .config console log report info [disk image] [vmlinux] [kernel image] ci-qemu-gce-upstream-auto possible deadlock in pcpu_alloc_noprof
2025/10/06 23:16 upstream c746c3b51698 8ef35d49 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in pcpu_alloc_noprof
2025/10/05 07:50 upstream 6093a688a07d 49379ee0 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in pcpu_alloc_noprof
2025/10/04 13:02 upstream 2ccb4d203fe4 49379ee0 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in pcpu_alloc_noprof
2025/10/01 03:52 upstream 4b81e2eb9e4d 65a0eece .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in pcpu_alloc_noprof
2025/09/30 00:40 upstream 449c2b302c8e 86341da6 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in pcpu_alloc_noprof
2025/09/29 20:57 upstream e5f0a698b34e 86341da6 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in pcpu_alloc_noprof
2025/09/24 23:19 upstream 4ea5af085908 0abd0691 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in pcpu_alloc_noprof
2025/09/21 14:46 upstream 3b08f56fbbb9 67c37560 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu2-arm64 possible deadlock in pcpu_alloc_noprof
2025/09/09 08:41 upstream f777d1112ee5 d291dd2d .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu2-arm64-compat possible deadlock in pcpu_alloc_noprof
2025/10/07 18:33 net f07f91a36090 8ef35d49 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce possible deadlock in pcpu_alloc_noprof
2025/10/07 12:46 net f07f91a36090 8ef35d49 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce possible deadlock in pcpu_alloc_noprof
2025/10/07 11:05 net f07f91a36090 8ef35d49 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce possible deadlock in pcpu_alloc_noprof
2025/10/07 10:29 net f07f91a36090 8ef35d49 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce possible deadlock in pcpu_alloc_noprof
2025/10/06 21:40 net 521405cb54cd 91305dbe .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce possible deadlock in pcpu_alloc_noprof
2025/10/06 00:20 net 1b54b0756f05 49379ee0 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce possible deadlock in pcpu_alloc_noprof
2025/10/05 12:54 net 1b54b0756f05 49379ee0 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce possible deadlock in pcpu_alloc_noprof
2025/10/05 10:43 net 1b54b0756f05 49379ee0 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce possible deadlock in pcpu_alloc_noprof
2025/10/04 18:35 net 1b54b0756f05 49379ee0 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce possible deadlock in pcpu_alloc_noprof
2025/10/04 09:33 net 1b54b0756f05 49379ee0 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce possible deadlock in pcpu_alloc_noprof
2025/10/04 04:12 net 1b54b0756f05 49379ee0 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce possible deadlock in pcpu_alloc_noprof
2025/10/03 22:13 net 1b54b0756f05 49379ee0 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce possible deadlock in pcpu_alloc_noprof
2025/10/03 06:26 net 07fdad3a9375 49379ee0 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce possible deadlock in pcpu_alloc_noprof
2025/10/03 03:05 net 07fdad3a9375 49379ee0 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce possible deadlock in pcpu_alloc_noprof
2025/10/02 05:09 net daa26ea63c6f a1859138 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce possible deadlock in pcpu_alloc_noprof
2025/10/01 10:50 net daa26ea63c6f 65a0eece .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce possible deadlock in pcpu_alloc_noprof
2025/10/01 01:24 net 2aff4420efc2 65a0eece .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce possible deadlock in pcpu_alloc_noprof
2025/09/30 20:58 net 2aff4420efc2 65a0eece .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce possible deadlock in pcpu_alloc_noprof
2025/09/30 12:30 net b9bd25f47eb7 86341da6 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce possible deadlock in pcpu_alloc_noprof
2025/09/30 11:21 net b9bd25f47eb7 86341da6 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce possible deadlock in pcpu_alloc_noprof
2025/09/30 05:58 net b9bd25f47eb7 86341da6 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce possible deadlock in pcpu_alloc_noprof
2025/09/30 01:46 net 012ea489aeda 86341da6 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce possible deadlock in pcpu_alloc_noprof
2025/09/29 22:09 net 012ea489aeda 86341da6 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce possible deadlock in pcpu_alloc_noprof
2025/09/29 19:26 net 012ea489aeda 86341da6 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce possible deadlock in pcpu_alloc_noprof
2025/10/06 20:29 net-next 07fdad3a9375 91305dbe .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in pcpu_alloc_noprof
2025/10/05 19:09 net-next 07fdad3a9375 49379ee0 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in pcpu_alloc_noprof
2025/10/04 22:30 net-next 07fdad3a9375 49379ee0 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in pcpu_alloc_noprof
2025/10/04 11:51 net-next 07fdad3a9375 49379ee0 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in pcpu_alloc_noprof
2025/10/03 19:59 net-next 07fdad3a9375 49379ee0 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in pcpu_alloc_noprof
2025/10/03 15:22 net-next 07fdad3a9375 49379ee0 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in pcpu_alloc_noprof
2025/10/03 11:35 net-next 07fdad3a9375 49379ee0 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in pcpu_alloc_noprof
2025/10/02 15:58 net-next f1455695d2d9 49379ee0 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in pcpu_alloc_noprof
2025/10/02 00:53 net-next f1455695d2d9 a1859138 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in pcpu_alloc_noprof
2025/09/30 07:51 net-next e8c4840d0c19 86341da6 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in pcpu_alloc_noprof
2025/10/07 05:16 linux-next 4a7153147192 8ef35d49 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-rust-kasan-gce possible deadlock in pcpu_alloc_noprof
2025/10/07 03:17 linux-next 4a7153147192 91305dbe .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-rust-kasan-gce possible deadlock in pcpu_alloc_noprof
2025/10/04 03:01 linux-next 47a8d4b89844 49379ee0 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-rust-kasan-gce possible deadlock in pcpu_alloc_noprof
2025/10/01 15:25 linux-next 3b9b1f8df454 a1859138 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-rust-kasan-gce possible deadlock in pcpu_alloc_noprof
2025/10/01 08:04 linux-next 3b9b1f8df454 65a0eece .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-rust-kasan-gce possible deadlock in pcpu_alloc_noprof
2025/09/30 01:48 linux-next 3b9b1f8df454 86341da6 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-rust-kasan-gce possible deadlock in pcpu_alloc_noprof
2025/06/22 14:19 linux-next 5d4809e25903 d6cdfb8a .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in pcpu_alloc_noprof
2025/10/02 03:23 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 2213e57a69f0 a1859138 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in pcpu_alloc_noprof
2025/07/06 10:18 git://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux.git for-next fda589c28604 4f67c4ae .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu2-riscv64 possible deadlock in pcpu_alloc_noprof
* Struck through repros no longer work on HEAD.