syzbot


INFO: task hung in reg_check_chans_work (7)

Status: upstream: reported C repro on 2024/09/23 08:39
Subsystems: wireless
[Documentation on labels]
Reported-by: syzbot+a2de4763f84f61499210@syzkaller.appspotmail.com
First crash: 224d, last: 2d06h
Cause bisection: failed (error log, bisect log)
  
Discussions (1)
Title Replies (including bot) Last reply
[syzbot] [wireless?] INFO: task hung in reg_check_chans_work (7) 0 (2) 2024/10/01 03:13
Similar bugs (23)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-5.15 INFO: task hung in reg_check_chans_work 10 104d 389d 0/3 auto-obsoleted due to no activity on 2025/02/14 20:30
linux-6.1 INFO: task hung in reg_check_chans_work (2) 1 60d 60d 0/3 upstream: reported on 2024/12/20 18:04
upstream INFO: task hung in reg_check_chans_work (6) wireless C error 129 227d 300d 26/28 fixed on 2024/07/09 19:14
upstream INFO: task hung in reg_check_chans_work (3) wireless 60 1172d 1235d 0/28 auto-closed as invalid on 2022/04/03 20:03
linux-4.14 INFO: task hung in reg_check_chans_work 1 1017d 1017d 0/1 auto-obsoleted due to no activity on 2022/09/05 08:58
upstream INFO: task hung in reg_check_chans_work (4) wireless 4 964d 967d 0/28 auto-closed as invalid on 2022/09/28 14:08
upstream INFO: task hung in reg_check_chans_work net 15 2502d 2561d 0/28 closed as dup on 2018/02/14 15:33
android-44 INFO: task hung in reg_check_chans_work 18 2474d 2547d 0/2 auto-closed as invalid on 2019/02/22 14:50
android-49 INFO: task hung in reg_check_chans_work 18 2473d 2571d 0/3 auto-closed as invalid on 2019/02/22 15:19
linux-6.1 INFO: task hung in reg_check_chans_work 3 251d 269d 0/3 auto-obsoleted due to no activity on 2024/09/20 17:51
upstream INFO: task hung in reg_check_chans_work (5) wireless 26 478d 607d 0/28 auto-obsoleted due to no activity on 2024/01/08 12:17
upstream INFO: task hung in reg_check_chans_work (2) wireless 3 1596d 1605d 0/28 auto-closed as invalid on 2021/01/04 12:48
linux-6.1 INFO: rcu detected stall in corrupted origin:upstream missing-backport C 3867 9d16h 708d 0/3 upstream: reported C repro on 2023/03/13 04:03
android-5-15 BUG: soft lockup in corrupted origin:upstream C error 33 157d 313d 0/2 upstream: reported C repro on 2024/04/11 09:01
upstream BUG: workqueue lockup (5) kernel C done 11435 10h02m 1862d 0/28 upstream: reported C repro on 2020/01/14 22:04
upstream INFO: task hung in nsim_destroy (4) net 421 4d06h 263d 0/28 upstream: reported on 2024/05/31 11:16
upstream INFO: task hung in reg_process_self_managed_hints wireless C done 218 10h02m 547d 0/28 upstream: reported C repro on 2023/08/21 16:36
upstream INFO: rcu detected stall in corrupted (4) net mm C done inconclusive 638 7d22h 1628d 0/28 upstream: reported C repro on 2020/09/04 18:49
linux-4.14 BUG: soft lockup in corrupted C error 12 933d 1416d 0/1 upstream: reported C repro on 2021/04/04 06:30
linux-4.19 INFO: rcu detected stall in corrupted C error 2 1125d 1832d 0/1 upstream: reported C repro on 2020/02/13 05:06
upstream INFO: task hung in uevent_show (2) kernel C inconclusive 6194 1h13m 101d 0/28 upstream: reported C repro on 2024/11/09 14:37
linux-4.19 BUG: soft lockup in corrupted C error 3 962d 1150d 0/1 upstream: reported C repro on 2021/12/26 20:46
linux-5.15 INFO: rcu detected stall in corrupted origin:lts-only C error 15 2d23h 484d 0/3 upstream: reported C repro on 2023/10/23 02:41

Sample crash report:
INFO: task kworker/0:0:8 blocked for more than 149 seconds.
      Not tainted 6.12.0-rc1-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:kworker/0:0     state:D stack:21392 pid:8     tgid:8     ppid:2      flags:0x00004000
Workqueue: events_power_efficient reg_check_chans_work
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5315 [inline]
 __schedule+0x1895/0x4b30 kernel/sched/core.c:6675
 __schedule_loop kernel/sched/core.c:6752 [inline]
 schedule+0x14b/0x320 kernel/sched/core.c:6767
 schedule_preempt_disabled+0x13/0x30 kernel/sched/core.c:6824
 __mutex_lock_common kernel/locking/mutex.c:684 [inline]
 __mutex_lock+0x6a7/0xd70 kernel/locking/mutex.c:752
 wiphy_lock include/net/cfg80211.h:6014 [inline]
 reg_leave_invalid_chans net/wireless/reg.c:2468 [inline]
 reg_check_chans_work+0x164/0xfd0 net/wireless/reg.c:2483
 process_one_work kernel/workqueue.c:3229 [inline]
 process_scheduled_works+0xa63/0x1850 kernel/workqueue.c:3310
 worker_thread+0x870/0xd30 kernel/workqueue.c:3391
 kthread+0x2f0/0x390 kernel/kthread.c:389
 ret_from_fork+0x4b/0x80 arch/x86/kernel/process.c:147
 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244
 </TASK>

Showing all locks held in the system:
1 lock held by kthreadd/2:
1 lock held by khungtaskd/30:
 #0: ffffffff8e937de0 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire include/linux/rcupdate.h:337 [inline]
 #0: ffffffff8e937de0 (rcu_read_lock){....}-{1:2}, at: rcu_read_lock include/linux/rcupdate.h:849 [inline]
 #0: ffffffff8e937de0 (rcu_read_lock){....}-{1:2}, at: debug_show_all_locks+0x55/0x2a0 kernel/locking/lockdep.c:6720
3 locks held by kworker/u8:3/52:
5 locks held by kworker/0:2/937:
3 locks held by kworker/u8:5/1067:
 #0: ffff8880b863ea98 (&rq->__lock){-.-.}-{2:2}, at: raw_spin_rq_lock_nested+0x2a/0x140 kernel/sched/core.c:593
 #1: ffff8880b8728948 (&per_cpu_ptr(group->pcpu, cpu)->seq){-.-.}-{0:0}, at: psi_task_switch+0x441/0x770 kernel/sched/psi.c:989
 #2: ffff8880b872a718 (&base->lock){-.-.}-{2:2}, at: lock_timer_base+0x112/0x240 kernel/time/timer.c:1051
5 locks held by kworker/u8:7/3017:
2 locks held by syslogd/4667:
1 lock held by klogd/4674:
4 locks held by dhcpcd/4899:
2 locks held by getty/4991:
 #0: ffff888031d9a0a0 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x25/0x70 drivers/tty/tty_ldisc.c:243
 #1: ffffc90002f062f0 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x6a6/0x1e00 drivers/tty/n_tty.c:2211
5 locks held by syz-executor223/5245:

=============================================

NMI backtrace for cpu 0
CPU: 0 UID: 0 PID: 30 Comm: khungtaskd Not tainted 6.12.0-rc1-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:94 [inline]
 dump_stack_lvl+0x241/0x360 lib/dump_stack.c:120
 nmi_cpu_backtrace+0x49c/0x4d0 lib/nmi_backtrace.c:113
 nmi_trigger_cpumask_backtrace+0x198/0x320 lib/nmi_backtrace.c:62
 trigger_all_cpu_backtrace include/linux/nmi.h:162 [inline]
 check_hung_uninterruptible_tasks kernel/hung_task.c:223 [inline]
 watchdog+0xff4/0x1040 kernel/hung_task.c:379
 kthread+0x2f0/0x390 kernel/kthread.c:389
 ret_from_fork+0x4b/0x80 arch/x86/kernel/process.c:147
 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244
 </TASK>
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1
CPU: 1 UID: 0 PID: 5245 Comm: syz-executor223 Not tainted 6.12.0-rc1-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024
RIP: 0010:__update_freelist_fast mm/slub.c:660 [inline]
RIP: 0010:slab_update_freelist mm/slub.c:730 [inline]
RIP: 0010:__slab_free+0x196/0x3d0 mm/slub.c:4432
Code: ea 48 8b 4c 24 20 4d 89 f8 e8 f6 dc ff ff 89 c3 eb 43 48 8b 5c 24 20 4c 89 f9 48 89 ea 4c 89 e0 48 8b 34 24 f0 48 0f c7 4e 20 <0f> 84 c3 00 00 00 eb 4e e8 5d 7d a9 ff 48 8b 3c 24 4c 89 e6 48 89
RSP: 0018:ffffc90003c370d0 EFLAGS: 00000242
RAX: ffff8880352399c0 RBX: ffff888035239a80 RCX: 0000000000400007
RDX: 0000000000400008 RSI: ffffea0000d48e40 RDI: ffff88801ac41780
RBP: 0000000000400008 R08: 0000000000000001 R09: ffffffff81fe9dcf
R10: dffffc0000000000 R11: fffffbfff2858b07 R12: ffff8880352399c0
R13: 0000000000000000 R14: 0000000000000001 R15: 0000000000400007
FS:  000055555f9ef480(0000) GS:ffff8880b8700000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000055d74c089050 CR3: 0000000078b74000 CR4: 00000000003526f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <NMI>
 </NMI>
 <TASK>
 qlink_free mm/kasan/quarantine.c:163 [inline]
 qlist_free_all+0x9a/0x140 mm/kasan/quarantine.c:179
 kasan_quarantine_reduce+0x14f/0x170 mm/kasan/quarantine.c:286
 __kasan_slab_alloc+0x23/0x80 mm/kasan/common.c:329
 kasan_slab_alloc include/linux/kasan.h:247 [inline]
 slab_post_alloc_hook mm/slub.c:4086 [inline]
 slab_alloc_node mm/slub.c:4135 [inline]
 kmem_cache_alloc_noprof+0x135/0x2a0 mm/slub.c:4142
 ptlock_alloc mm/memory.c:6902 [inline]
 ptlock_init include/linux/mm.h:2958 [inline]
 pmd_ptlock_init include/linux/mm.h:3062 [inline]
 pagetable_pmd_ctor include/linux/mm.h:3100 [inline]
 pmd_alloc_one_noprof include/asm-generic/pgalloc.h:141 [inline]
 __pmd_alloc+0x110/0x620 mm/memory.c:6315
 pmd_alloc include/linux/mm.h:2849 [inline]
 copy_pmd_range+0x8135/0x85f0 mm/memory.c:1235
 copy_pud_range mm/memory.c:1292 [inline]
 copy_p4d_range mm/memory.c:1316 [inline]
 copy_page_range+0x99f/0xe90 mm/memory.c:1414
 dup_mmap kernel/fork.c:750 [inline]
 dup_mm kernel/fork.c:1674 [inline]
 copy_mm+0x11fb/0x1f40 kernel/fork.c:1723
 copy_process+0x1845/0x3d50 kernel/fork.c:2375
 kernel_clone+0x226/0x8f0 kernel/fork.c:2787
 __do_sys_clone kernel/fork.c:2930 [inline]
 __se_sys_clone kernel/fork.c:2914 [inline]
 __x64_sys_clone+0x258/0x2a0 kernel/fork.c:2914
 do_syscall_x64 arch/x86/entry/common.c:52 [inline]
 do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7efde123ccf3
Code: 1f 84 00 00 00 00 00 64 48 8b 04 25 10 00 00 00 45 31 c0 31 d2 31 f6 bf 11 00 20 01 4c 8d 90 d0 02 00 00 b8 38 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 35 89 c2 85 c0 75 2c 64 48 8b 04 25 10 00 00
RSP: 002b:00007ffda41bff68 EFLAGS: 00000246 ORIG_RAX: 0000000000000038
RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007efde123ccf3
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000001200011
RBP: 0000000000000001 R08: 0000000000000000 R09: 00007ffda41bfe07
R10: 000055555f9ef750 R11: 0000000000000246 R12: 0000000000000000
R13: 00007ffda41c00a0 R14: 00007ffda41c00e0 R15: 0000000000000002
 </TASK>
INFO: NMI handler (nmi_cpu_backtrace_handler) took too long to run: 1.825 msecs

Crashes (388):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2024/10/01 03:13 upstream 9852d85ec9d4 bbd4e0a4 .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in reg_check_chans_work
2024/11/01 03:49 upstream 90602c251cda 96eb609f .config console log report syz / log C [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root INFO: task hung in reg_check_chans_work
2024/10/27 03:32 upstream 850925a8133c 65e8686b .config console log report syz / log C [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root INFO: task hung in reg_check_chans_work
2024/10/25 14:09 upstream ae90f6a6170d 2a61f980 .config console log report syz / log C [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root INFO: task hung in reg_check_chans_work
2024/11/03 11:51 upstream 3e5e6c9900c3 f00eed24 .config console log report syz / log [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in reg_check_chans_work
2024/09/18 04:51 upstream 2f27fce67173 c673ca06 .config console log report syz / log [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in reg_check_chans_work
2025/02/12 18:57 upstream 09fbf3d50205 b27c2402 .config console log report syz / log [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root INFO: task hung in reg_check_chans_work
2025/02/09 12:06 upstream 9946eaf552b1 ef44b750 .config console log report syz / log [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root INFO: task hung in reg_check_chans_work
2024/11/28 12:28 upstream b86545e02e8c 5df23865 .config console log report syz / log [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root INFO: task hung in reg_check_chans_work
2024/11/11 19:32 upstream 2d5404caa8c7 0c4b1325 .config console log report syz / log [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root INFO: task hung in reg_check_chans_work
2024/11/07 08:55 upstream 7758b206117d df3dc63b .config console log report syz / log [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root INFO: task hung in reg_check_chans_work
2024/11/03 01:22 upstream 11066801dd4b f00eed24 .config console log report syz / log [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root INFO: task hung in reg_check_chans_work
2024/10/10 17:32 net a354733c738d 8fbfc0c8 .config console log report syz / log [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce INFO: task hung in reg_check_chans_work
2024/10/20 19:40 linux-next 15e7d45e786a cd6fc0a3 .config console log report syz / log [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in reg_check_chans_work
2025/02/16 19:46 upstream ad1b832bf1cf 40a34ec9 .config console log report info [disk image] [vmlinux] [kernel image] ci-qemu-gce-upstream-auto INFO: task hung in reg_check_chans_work
2025/02/15 05:09 upstream 04f41cbf03ec 40a34ec9 .config console log report info [disk image] [vmlinux] [kernel image] ci-qemu-gce-upstream-auto INFO: task hung in reg_check_chans_work
2025/02/14 01:24 upstream ab68d7eb7b1a d9a046cf .config console log report info [disk image] [vmlinux] [kernel image] ci-qemu-gce-upstream-auto INFO: task hung in reg_check_chans_work
2025/02/11 00:19 upstream febbc555cf0f 43f51a00 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in reg_check_chans_work
2025/02/09 16:08 upstream 9946eaf552b1 ef44b750 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in reg_check_chans_work
2025/02/09 00:55 upstream 9946eaf552b1 ef44b750 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root INFO: task hung in reg_check_chans_work
2025/02/08 06:53 upstream 7ee983c850b4 a4f327c2 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in reg_check_chans_work
2025/02/07 09:39 upstream bb066fe812d6 53657d1b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root INFO: task hung in reg_check_chans_work
2025/02/07 05:02 upstream bb066fe812d6 53657d1b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in reg_check_chans_work
2025/02/06 13:25 upstream 92514ef226f5 577d049b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root INFO: task hung in reg_check_chans_work
2025/02/06 08:22 upstream 92514ef226f5 577d049b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in reg_check_chans_work
2025/02/04 05:55 upstream 0de63bb7d919 8f267cef .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in reg_check_chans_work
2025/02/04 03:57 upstream 0de63bb7d919 a21a8419 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in reg_check_chans_work
2025/02/02 13:51 upstream 69e858e0b8b2 568559e4 .config console log report info [disk image] [vmlinux] [kernel image] ci-qemu-gce-upstream-auto INFO: task hung in reg_check_chans_work
2025/02/01 22:01 upstream 69e858e0b8b2 0dff8567 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in reg_check_chans_work
2025/02/01 13:09 upstream 69e858e0b8b2 0dff8567 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in reg_check_chans_work
2025/02/01 12:51 upstream 69e858e0b8b2 0dff8567 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in reg_check_chans_work
2025/02/01 04:39 upstream 69e858e0b8b2 aa47157c .config console log report info [disk image] [vmlinux] [kernel image] ci-qemu-gce-upstream-auto INFO: task hung in reg_check_chans_work
2025/01/31 17:47 upstream 69e858e0b8b2 aa47157c .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in reg_check_chans_work
2025/01/30 16:07 upstream 72deda0abee6 e961d16c .config console log report info [disk image] [vmlinux] [kernel image] ci-qemu-gce-upstream-auto INFO: task hung in reg_check_chans_work
2025/01/28 01:37 upstream 9c5968db9e62 18070896 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in reg_check_chans_work
2025/01/27 03:03 upstream c2da8b3f914f 9fbd772e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root INFO: task hung in reg_check_chans_work
2025/01/26 01:18 upstream b46c89c08f41 9fbd772e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in reg_check_chans_work
2025/01/22 21:31 upstream c4b9570cfb63 25e17fd3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in reg_check_chans_work
2025/01/22 10:42 upstream 62de6e168526 da72ac06 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in reg_check_chans_work
2025/01/22 02:10 upstream 62de6e168526 da72ac06 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root INFO: task hung in reg_check_chans_work
2025/01/20 09:22 upstream ffd294d346d1 f2cb035c .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root INFO: task hung in reg_check_chans_work
2025/01/19 15:33 upstream fda5e3f28400 f2cb035c .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in reg_check_chans_work
2025/01/19 10:05 upstream fda5e3f28400 f2cb035c .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root INFO: task hung in reg_check_chans_work
2025/01/18 15:48 upstream 595523945be0 f2cb035c .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in reg_check_chans_work
2025/01/13 21:28 upstream c45323b7560e b1f1cd88 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in reg_check_chans_work
2025/01/06 23:14 upstream 5428dc1906dd f3558dbf .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in reg_check_chans_work
2025/01/03 23:22 upstream 0bc21e701a6f f3558dbf .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in reg_check_chans_work
2025/01/02 04:54 upstream 56e6a3499e14 d3ccff63 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in reg_check_chans_work
2024/12/29 04:24 upstream 059dd502b263 d3ccff63 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root INFO: task hung in reg_check_chans_work
2024/08/20 23:17 upstream 521b1e7f4cf0 9f0ab3fb .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in reg_check_chans_work
2025/02/02 07:46 upstream 69e858e0b8b2 0dff8567 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-386 INFO: task hung in reg_check_chans_work
2025/01/17 20:32 upstream 9bffa1ad25b8 953d1c45 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-386 INFO: task hung in reg_check_chans_work
2025/01/17 17:47 upstream 9bffa1ad25b8 953d1c45 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-386 INFO: task hung in reg_check_chans_work
2025/01/24 06:14 net 15a901361ec3 521b0ce3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce INFO: task hung in reg_check_chans_work
2025/01/23 13:42 net 0ad9617c78ac 9d4f14f8 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce INFO: task hung in reg_check_chans_work
2025/01/21 15:09 net d640627663bf 6e87cfa2 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce INFO: task hung in reg_check_chans_work
2025/01/19 03:42 net bc50835e83f6 f2cb035c .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce INFO: task hung in reg_check_chans_work
2025/01/17 23:54 net 5d6a361dc01d 953d1c45 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce INFO: task hung in reg_check_chans_work
2025/01/16 20:24 net cbc16bceea78 968edaf4 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce INFO: task hung in reg_check_chans_work
2025/01/08 09:28 net db78475ba0d3 f3558dbf .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce INFO: task hung in reg_check_chans_work
2025/02/16 16:34 net-next 0784d83df3bf 40a34ec9 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce INFO: task hung in reg_check_chans_work
2025/01/08 02:20 net-next 912d6f669725 f3558dbf .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce INFO: task hung in reg_check_chans_work
2025/01/06 08:06 net-next 3e5908172c05 f3558dbf .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce INFO: task hung in reg_check_chans_work
2025/01/02 22:06 net-next 9268abe611b0 d3ccff63 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce INFO: task hung in reg_check_chans_work
2025/02/05 07:12 linux-next ed88b8b82c53 5896748e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in reg_check_chans_work
2025/02/03 15:23 linux-next 00f3246adeea a21a8419 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in reg_check_chans_work
2024/11/04 12:17 https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git usb-testing bf373d2919d9 f00eed24 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-usb INFO: task hung in reg_check_chans_work
2025/02/13 10:38 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 2014c95afece 2afad16e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 INFO: task hung in reg_check_chans_work
2025/02/13 06:19 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 2014c95afece b27c2402 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 INFO: task hung in reg_check_chans_work
2025/02/09 09:44 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 2014c95afece ef44b750 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 INFO: task hung in reg_check_chans_work
2025/02/07 11:04 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 2014c95afece 53657d1b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 INFO: task hung in reg_check_chans_work
2025/02/07 06:32 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 2014c95afece 53657d1b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 INFO: task hung in reg_check_chans_work
2025/02/05 13:55 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 2014c95afece 5896748e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 INFO: task hung in reg_check_chans_work
* Struck through repros no longer work on HEAD.