syzbot


INFO: task hung in linkwatch_event (3)

Status: upstream: reported on 2022/11/22 17:04
Labels: net (incorrect?)
Reported-by: syzbot+d4b2f8282f84f54e87a1@syzkaller.appspotmail.com
First crash: 381d, last: 6d15h
Discussions (1)
Title Replies (including bot) Last reply
[syzbot] INFO: task hung in linkwatch_event (3) 0 (1) 2022/11/22 17:04
Similar bugs (11)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
android-414 INFO: task hung in linkwatch_event C 7 1291d 1510d 0/1 public: reported C repro on 2019/04/10 16:14
linux-4.14 INFO: task hung in linkwatch_event (2) 1 312d 312d 0/1 auto-obsoleted due to no activity on 2022/11/19 11:58
android-44 INFO: task hung in linkwatch_event 6 1726d 1872d 0/2 auto-closed as invalid on 2019/03/05 13:11
upstream INFO: task hung in linkwatch_event C 82 1319d 1930d 0/24 closed as dup on 2018/02/14 15:33
linux-4.14 INFO: task hung in linkwatch_event 5 995d 1122d 0/1 auto-closed as invalid on 2021/01/05 01:42
linux-4.19 INFO: task hung in linkwatch_event (2) C error 217 86d 1174d 0/1 upstream: reported C repro on 2020/03/11 20:12
upstream INFO: task hung in linkwatch_event (2) net C done done 1033 400d 1126d 22/24 fixed on 2022/05/13 11:13
linux-4.19 INFO: task hung in linkwatch_event 3 1328d 1442d 0/1 auto-closed as invalid on 2020/02/07 01:11
linux-4.14 INFO: task hung in linkwatch_event (3) 2 146d 147d 0/1 upstream: reported on 2023/01/03 10:49
android-49 INFO: task hung in linkwatch_event 13 1490d 1507d 0/3 auto-closed as invalid on 2019/10/25 08:50
linux-6.1 INFO: task hung in linkwatch_event 1 48d 48d 0/3 upstream: reported on 2023/04/12 08:24

Sample crash report:
INFO: task kworker/0:2:900 blocked for more than 143 seconds.
      Not tainted 6.4.0-rc3-syzkaller-00008-gae8373a5add4 #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:kworker/0:2     state:D stack:23568 pid:900   ppid:2      flags:0x00004000
Workqueue: events linkwatch_event
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5343 [inline]
 __schedule+0xc9a/0x5880 kernel/sched/core.c:6669
 schedule+0xde/0x1a0 kernel/sched/core.c:6745
 schedule_preempt_disabled+0x13/0x20 kernel/sched/core.c:6804
 __mutex_lock_common kernel/locking/mutex.c:679 [inline]
 __mutex_lock+0xa3b/0x1350 kernel/locking/mutex.c:747
 linkwatch_event+0xf/0x70 net/core/link_watch.c:277
 process_one_work+0x99a/0x15e0 kernel/workqueue.c:2405
 worker_thread+0x67d/0x10c0 kernel/workqueue.c:2552
 kthread+0x344/0x440 kernel/kthread.c:379
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:308
 </TASK>
INFO: task dhcpcd:4671 blocked for more than 143 seconds.
      Not tainted 6.4.0-rc3-syzkaller-00008-gae8373a5add4 #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:dhcpcd          state:D stack:23240 pid:4671  ppid:4670   flags:0x00004002
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5343 [inline]
 __schedule+0xc9a/0x5880 kernel/sched/core.c:6669
 schedule+0xde/0x1a0 kernel/sched/core.c:6745
 schedule_preempt_disabled+0x13/0x20 kernel/sched/core.c:6804
 __mutex_lock_common kernel/locking/mutex.c:679 [inline]
 __mutex_lock+0xa3b/0x1350 kernel/locking/mutex.c:747
 devinet_ioctl+0x1c4/0x1df0 net/ipv4/devinet.c:1074
 inet_ioctl+0x33f/0x380 net/ipv4/af_inet.c:977
 sock_do_ioctl+0xcc/0x230 net/socket.c:1201
 sock_ioctl+0x1f8/0x680 net/socket.c:1318
 vfs_ioctl fs/ioctl.c:51 [inline]
 __do_sys_ioctl fs/ioctl.c:870 [inline]
 __se_sys_ioctl fs/ioctl.c:856 [inline]
 __x64_sys_ioctl+0x197/0x210 fs/ioctl.c:856
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x39/0xb0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7feb9478cd49
RSP: 002b:00007ffebf6398e8 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007feb946be6c0 RCX: 00007feb9478cd49
RDX: 00007ffebf649ad8 RSI: 0000000000008914 RDI: 0000000000000018
RBP: 00007ffebf659c98 R08: 00007ffebf649a98 R09: 00007ffebf649a48
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007ffebf649ad8 R14: 0000000000000028 R15: 0000000000008914
 </TASK>
INFO: task kworker/1:8:5115 blocked for more than 143 seconds.
      Not tainted 6.4.0-rc3-syzkaller-00008-gae8373a5add4 #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:kworker/1:8     state:D stack:23704 pid:5115  ppid:2      flags:0x00004000
Workqueue: events switchdev_deferred_process_work
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5343 [inline]
 __schedule+0xc9a/0x5880 kernel/sched/core.c:6669
 schedule+0xde/0x1a0 kernel/sched/core.c:6745
 schedule_preempt_disabled+0x13/0x20 kernel/sched/core.c:6804
 __mutex_lock_common kernel/locking/mutex.c:679 [inline]
 __mutex_lock+0xa3b/0x1350 kernel/locking/mutex.c:747
 switchdev_deferred_process_work+0xe/0x20 net/switchdev/switchdev.c:75
 process_one_work+0x99a/0x15e0 kernel/workqueue.c:2405
 worker_thread+0x67d/0x10c0 kernel/workqueue.c:2552
 kthread+0x344/0x440 kernel/kthread.c:379
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:308
 </TASK>
INFO: task syz-executor.0:20565 blocked for more than 144 seconds.
      Not tainted 6.4.0-rc3-syzkaller-00008-gae8373a5add4 #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.0  state:D stack:24688 pid:20565 ppid:1      flags:0x00000004
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5343 [inline]
 __schedule+0xc9a/0x5880 kernel/sched/core.c:6669
 schedule+0xde/0x1a0 kernel/sched/core.c:6745
 schedule_preempt_disabled+0x13/0x20 kernel/sched/core.c:6804
 __mutex_lock_common kernel/locking/mutex.c:679 [inline]
 __mutex_lock+0xa3b/0x1350 kernel/locking/mutex.c:747
 rtnl_lock net/core/rtnetlink.c:78 [inline]
 rtnetlink_rcv_msg+0x3e8/0xd50 net/core/rtnetlink.c:6392
 netlink_rcv_skb+0x165/0x440 net/netlink/af_netlink.c:2546
 netlink_unicast_kernel net/netlink/af_netlink.c:1339 [inline]
 netlink_unicast+0x547/0x7f0 net/netlink/af_netlink.c:1365
 netlink_sendmsg+0x925/0xe30 net/netlink/af_netlink.c:1913
 sock_sendmsg_nosec net/socket.c:724 [inline]
 sock_sendmsg+0xde/0x190 net/socket.c:747
 __sys_sendto+0x23a/0x340 net/socket.c:2144
 __do_sys_sendto net/socket.c:2156 [inline]
 __se_sys_sendto net/socket.c:2152 [inline]
 __x64_sys_sendto+0xe1/0x1b0 net/socket.c:2152
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x39/0xb0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7f1f1103e19c
RSP: 002b:00007f1f112cf650 EFLAGS: 00000293 ORIG_RAX: 000000000000002c
RAX: ffffffffffffffda RBX: 00007f1f11cd4620 RCX: 00007f1f1103e19c
RDX: 0000000000000068 RSI: 00007f1f11cd4670 RDI: 0000000000000003
RBP: 0000000000000000 R08: 00007f1f112cf6a4 R09: 000000000000000c
R10: 0000000000000000 R11: 0000000000000293 R12: 0000000000000000
R13: 00007f1f11cd4670 R14: 0000000000000003 R15: 0000000000000000
 </TASK>

Showing all locks held in the system:
5 locks held by kworker/u4:1/12:
1 lock held by rcu_tasks_kthre/13:
 #0: ffffffff8c7984b0 (rcu_tasks.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x31/0xd80 kernel/rcu/tasks.h:518
1 lock held by rcu_tasks_trace/14:
 #0: ffffffff8c7981b0 (rcu_tasks_trace.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x31/0xd80 kernel/rcu/tasks.h:518
1 lock held by khungtaskd/28:
 #0: ffffffff8c7990c0 (rcu_read_lock){....}-{1:2}, at: debug_show_all_locks+0x55/0x340 kernel/locking/lockdep.c:6545
3 locks held by kworker/0:2/900:
 #0: ffff888012470d38 ((wq_completion)events){+.+.}-{0:0}, at: arch_atomic64_set arch/x86/include/asm/atomic64_64.h:34 [inline]
 #0: ffff888012470d38 ((wq_completion)events){+.+.}-{0:0}, at: arch_atomic_long_set include/linux/atomic/atomic-long.h:41 [inline]
 #0: ffff888012470d38 ((wq_completion)events){+.+.}-{0:0}, at: atomic_long_set include/linux/atomic/atomic-instrumented.h:1324 [inline]
 #0: ffff888012470d38 ((wq_completion)events){+.+.}-{0:0}, at: set_work_data kernel/workqueue.c:643 [inline]
 #0: ffff888012470d38 ((wq_completion)events){+.+.}-{0:0}, at: set_work_pool_and_clear_pending kernel/workqueue.c:670 [inline]
 #0: ffff888012470d38 ((wq_completion)events){+.+.}-{0:0}, at: process_one_work+0x883/0x15e0 kernel/workqueue.c:2376
 #1: ffffc9000529fdb0 ((linkwatch_work).work){+.+.}-{0:0}, at: process_one_work+0x8b7/0x15e0 kernel/workqueue.c:2380
 #2: ffffffff8e115028 (rtnl_mutex){+.+.}-{3:3}, at: linkwatch_event+0xf/0x70 net/core/link_watch.c:277
1 lock held by dhcpcd/4671:
 #0: ffffffff8e115028 (rtnl_mutex){+.+.}-{3:3}, at: devinet_ioctl+0x1c4/0x1df0 net/ipv4/devinet.c:1074
2 locks held by getty/4756:
 #0: ffff88802876d098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x26/0x80 drivers/tty/tty_ldisc.c:243
 #1: ffffc900015a02f0 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0xef4/0x13e0 drivers/tty/n_tty.c:2176
3 locks held by kworker/1:8/5115:
 #0: ffff888012470d38 ((wq_completion)events){+.+.}-{0:0}, at: arch_atomic64_set arch/x86/include/asm/atomic64_64.h:34 [inline]
 #0: ffff888012470d38 ((wq_completion)events){+.+.}-{0:0}, at: arch_atomic_long_set include/linux/atomic/atomic-long.h:41 [inline]
 #0: ffff888012470d38 ((wq_completion)events){+.+.}-{0:0}, at: atomic_long_set include/linux/atomic/atomic-instrumented.h:1324 [inline]
 #0: ffff888012470d38 ((wq_completion)events){+.+.}-{0:0}, at: set_work_data kernel/workqueue.c:643 [inline]
 #0: ffff888012470d38 ((wq_completion)events){+.+.}-{0:0}, at: set_work_pool_and_clear_pending kernel/workqueue.c:670 [inline]
 #0: ffff888012470d38 ((wq_completion)events){+.+.}-{0:0}, at: process_one_work+0x883/0x15e0 kernel/workqueue.c:2376
 #1: ffffc90005207db0 (deferred_process_work){+.+.}-{0:0}, at: process_one_work+0x8b7/0x15e0 kernel/workqueue.c:2380
 #2: ffffffff8e115028 (rtnl_mutex){+.+.}-{3:3}, at: switchdev_deferred_process_work+0xe/0x20 net/switchdev/switchdev.c:75
3 locks held by kworker/0:3/19020:
 #0: ffff88814ae44138 ((wq_completion)ipv6_addrconf){+.+.}-{0:0}, at: arch_atomic64_set arch/x86/include/asm/atomic64_64.h:34 [inline]
 #0: ffff88814ae44138 ((wq_completion)ipv6_addrconf){+.+.}-{0:0}, at: arch_atomic_long_set include/linux/atomic/atomic-long.h:41 [inline]
 #0: ffff88814ae44138 ((wq_completion)ipv6_addrconf){+.+.}-{0:0}, at: atomic_long_set include/linux/atomic/atomic-instrumented.h:1324 [inline]
 #0: ffff88814ae44138 ((wq_completion)ipv6_addrconf){+.+.}-{0:0}, at: set_work_data kernel/workqueue.c:643 [inline]
 #0: ffff88814ae44138 ((wq_completion)ipv6_addrconf){+.+.}-{0:0}, at: set_work_pool_and_clear_pending kernel/workqueue.c:670 [inline]
 #0: ffff88814ae44138 ((wq_completion)ipv6_addrconf){+.+.}-{0:0}, at: process_one_work+0x883/0x15e0 kernel/workqueue.c:2376
 #1: ffffc9000bc87db0 ((work_completion)(&(&net->ipv6.addr_chk_work)->work)){+.+.}-{0:0}, at: process_one_work+0x8b7/0x15e0 kernel/workqueue.c:2380
 #2: ffffffff8e115028 (rtnl_mutex){+.+.}-{3:3}, at: addrconf_verify_work+0x12/0x30 net/ipv6/addrconf.c:4630
3 locks held by kworker/1:4/28075:
 #0: ffff88814ae44138 ((wq_completion)ipv6_addrconf){+.+.}-{0:0}, at: arch_atomic64_set arch/x86/include/asm/atomic64_64.h:34 [inline]
 #0: ffff88814ae44138 ((wq_completion)ipv6_addrconf){+.+.}-{0:0}, at: arch_atomic_long_set include/linux/atomic/atomic-long.h:41 [inline]
 #0: ffff88814ae44138 ((wq_completion)ipv6_addrconf){+.+.}-{0:0}, at: atomic_long_set include/linux/atomic/atomic-instrumented.h:1324 [inline]
 #0: ffff88814ae44138 ((wq_completion)ipv6_addrconf){+.+.}-{0:0}, at: set_work_data kernel/workqueue.c:643 [inline]
 #0: ffff88814ae44138 ((wq_completion)ipv6_addrconf){+.+.}-{0:0}, at: set_work_pool_and_clear_pending kernel/workqueue.c:670 [inline]
 #0: ffff88814ae44138 ((wq_completion)ipv6_addrconf){+.+.}-{0:0}, at: process_one_work+0x883/0x15e0 kernel/workqueue.c:2376
 #1: ffffc900036bfdb0 ((work_completion)(&(&net->ipv6.addr_chk_work)->work)){+.+.}-{0:0}, at: process_one_work+0x8b7/0x15e0 kernel/workqueue.c:2380
 #2: ffffffff8e115028 (rtnl_mutex){+.+.}-{3:3}, at: addrconf_verify_work+0x12/0x30 net/ipv6/addrconf.c:4630
2 locks held by kworker/u4:8/19658:
1 lock held by syz-executor.0/20565:
 #0: ffffffff8e115028 (rtnl_mutex){+.+.}-{3:3}, at: rtnl_lock net/core/rtnetlink.c:78 [inline]
 #0: ffffffff8e115028 (rtnl_mutex){+.+.}-{3:3}, at: rtnetlink_rcv_msg+0x3e8/0xd50 net/core/rtnetlink.c:6392
2 locks held by syz-executor.0/20596:
 #0: ffffffff8e101650 (pernet_ops_rwsem){++++}-{3:3}, at: copy_net_ns+0x4cb/0x8e0 net/core/net_namespace.c:487
 #1: ffffffff8e115028 (rtnl_mutex){+.+.}-{3:3}, at: smc_pnet_create_pnetids_list net/smc/smc_pnet.c:809 [inline]
 #1: ffffffff8e115028 (rtnl_mutex){+.+.}-{3:3}, at: smc_pnet_net_init+0x131/0x230 net/smc/smc_pnet.c:878
2 locks held by syz-executor.0/20600:
 #0: ffffffff8e101650 (pernet_ops_rwsem){++++}-{3:3}, at: copy_net_ns+0x4cb/0x8e0 net/core/net_namespace.c:487
 #1: ffffffff8e115028 (rtnl_mutex){+.+.}-{3:3}, at: smc_pnet_create_pnetids_list net/smc/smc_pnet.c:809 [inline]
 #1: ffffffff8e115028 (rtnl_mutex){+.+.}-{3:3}, at: smc_pnet_net_init+0x131/0x230 net/smc/smc_pnet.c:878

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

NMI backtrace for cpu 1
CPU: 1 PID: 28 Comm: khungtaskd Not tainted 6.4.0-rc3-syzkaller-00008-gae8373a5add4 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/28/2023
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0xd9/0x150 lib/dump_stack.c:106
 nmi_cpu_backtrace+0x29c/0x350 lib/nmi_backtrace.c:113
 nmi_trigger_cpumask_backtrace+0x2a4/0x300 lib/nmi_backtrace.c:62
 trigger_all_cpu_backtrace include/linux/nmi.h:148 [inline]
 check_hung_uninterruptible_tasks kernel/hung_task.c:222 [inline]
 watchdog+0xe16/0x1090 kernel/hung_task.c:379
 kthread+0x344/0x440 kernel/kthread.c:379
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:308
 </TASK>
Sending NMI from CPU 1 to CPUs 0:
NMI backtrace for cpu 0
CPU: 0 PID: 19658 Comm: kworker/u4:8 Not tainted 6.4.0-rc3-syzkaller-00008-gae8373a5add4 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/28/2023
Workqueue: bat_events batadv_nc_worker
RIP: 0010:lock_release+0x35/0x670 kernel/locking/lockdep.c:5699
Code: fc ff df 41 57 41 56 41 55 41 54 49 89 fc 55 53 48 81 ec 90 00 00 00 48 8d 6c 24 10 48 89 74 24 08 48 c7 44 24 10 b3 8a b5 41 <48> c1 ed 03 48 c7 44 24 18 b0 15 f0 8b 48 01 e8 48 c7 44 24 20 90
RSP: 0018:ffffc90005b77b48 EFLAGS: 00000286
RAX: dffffc0000000000 RBX: ffff88802e979cc0 RCX: 0000000000000000
RDX: ffff88809b8d5940 RSI: ffffffff89da745c RDI: ffff88802e979cd8
RBP: ffffc90005b77b58 R08: 0000000000000001 R09: 0000000000000003
R10: fffff52000b6ef76 R11: 0000000000000000 R12: ffff88802e979cd8
R13: ffff88807e1c0c80 R14: dffffc0000000000 R15: ffffffff89da7650
FS:  0000000000000000(0000) GS:ffff8880b9800000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fb61f0d5000 CR3: 000000000c571000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 __raw_spin_unlock_bh include/linux/spinlock_api_smp.h:165 [inline]
 _raw_spin_unlock_bh+0x16/0x30 kernel/locking/spinlock.c:210
 spin_unlock_bh include/linux/spinlock.h:395 [inline]
 batadv_nc_purge_paths+0x1cc/0x3c0 net/batman-adv/network-coding.c:471
 batadv_nc_worker+0x931/0xfe0 net/batman-adv/network-coding.c:722
 process_one_work+0x99a/0x15e0 kernel/workqueue.c:2405
 worker_thread+0x67d/0x10c0 kernel/workqueue.c:2552
 kthread+0x344/0x440 kernel/kthread.c:379
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:308
 </TASK>

Crashes (115):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets Manager Title
2023/05/23 20:13 upstream ae8373a5add4 4bce1a3e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in linkwatch_event
2023/05/21 14:56 upstream 0dd2a6fb1e34 4bce1a3e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in linkwatch_event
2023/05/19 11:43 upstream 2d1bcbc6cd70 3bb7af1d .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in linkwatch_event
2023/05/13 03:46 upstream 9a48d6046722 2b9ba477 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in linkwatch_event
2023/04/30 02:13 upstream 1ae78a14516b 62df2017 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in linkwatch_event
2023/04/28 15:09 upstream 33afd4b76393 457a6e0a .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root INFO: task hung in linkwatch_event
2023/04/16 08:39 upstream a7a55e27ad72 ec410564 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root INFO: task hung in linkwatch_event
2023/04/15 08:38 upstream 95abc817ab3a ec410564 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in linkwatch_event
2023/04/13 09:11 upstream 0bcc40255504 82d5e53e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in linkwatch_event
2023/03/27 07:02 upstream 197b6b60ae7b fbf0499a .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in linkwatch_event
2023/03/26 08:48 upstream da8e7da11e4b fbf0499a .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in linkwatch_event
2023/03/15 12:04 upstream 6015b1aca1a2 18b58603 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in linkwatch_event
2023/03/03 08:00 upstream 04a357b1f6f0 f8902b57 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in linkwatch_event
2023/02/03 20:48 upstream 7b753a909f42 1b2f701a .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in linkwatch_event
2023/01/28 06:34 upstream 83abd4d4c4be 9dfcf09c .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root INFO: task hung in linkwatch_event
2023/01/24 11:51 upstream 7bf70dbb1882 9dfcf09c .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in linkwatch_event
2022/12/26 10:57 upstream 1b929c02afd3 9da18ae8 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in linkwatch_event
2022/10/10 22:48 upstream 4899a36f91a9 aea5da89 .config console log report info [disk image] [vmlinux] ci-upstream-kasan-gce INFO: task hung in linkwatch_event
2022/07/10 14:33 upstream b1c428b6c368 b5765a15 .config console log report info ci-upstream-kasan-gce-selinux-root INFO: task hung in linkwatch_event
2022/10/22 17:41 upstream 4da34b7d175d c0b80a55 .config console log report info [disk image] [vmlinux] ci-upstream-kasan-gce-386 INFO: task hung in linkwatch_event
2023/05/17 16:49 net 6ad85ed0ebf7 eaac4681 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce INFO: task hung in linkwatch_event
2023/04/12 22:17 net 136f36c74b03 82d5e53e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce INFO: task hung in linkwatch_event
2023/03/23 23:58 net b1de5c78ebe9 f94b4a29 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce INFO: task hung in linkwatch_event
2023/03/09 15:06 net 2d8cb0bfca6a f08b59ac .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce INFO: task hung in linkwatch_event
2023/02/25 11:18 net-old fd2a55e74a99 ee50e71c .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce INFO: task hung in linkwatch_event
2023/02/24 01:24 net-old fd2a55e74a99 9e2ebb3c .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce INFO: task hung in linkwatch_event
2023/01/28 13:59 net-old 28b4387f0ec0 9dfcf09c .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce INFO: task hung in linkwatch_event
2022/11/29 11:32 net-old d5082d386eee ca9683b8 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce INFO: task hung in linkwatch_event
2023/05/18 11:47 net-next af2eab1a8243 3bb7af1d .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce INFO: task hung in linkwatch_event
2023/05/16 09:41 net-next 6d4ff8aed3b3 71b00cfb .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce INFO: task hung in linkwatch_event
2023/04/24 08:20 net-next fd84c569f7b8 2b32bd34 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce INFO: task hung in linkwatch_event
2023/04/18 03:59 net-next 99676a576641 436577a9 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce INFO: task hung in linkwatch_event
2023/04/10 14:03 net-next 490fde262f17 71147e29 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce INFO: task hung in linkwatch_event
2023/04/03 19:04 net-next 7b600f8da8fe 7db618d0 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce INFO: task hung in linkwatch_event
2023/03/25 12:18 net-next bc77f7318da8 fbf0499a .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce INFO: task hung in linkwatch_event
2023/02/18 08:40 net-next-old 675f176b4dcc d02e9a70 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce INFO: task hung in linkwatch_event
2023/01/28 05:11 net-next-old c2ea552065e4 9dfcf09c .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce INFO: task hung in linkwatch_event
2022/12/21 01:44 net-next-old 9054b41c4e1b d3e76707 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce INFO: task hung in linkwatch_event
2022/11/21 19:43 net-next-old 8719a1c30d3a 1c576c23 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce INFO: task hung in linkwatch_event
2022/11/19 10:37 net-next-old ab0377803daf 5bb70014 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce INFO: task hung in linkwatch_event
2022/11/16 15:17 net-next-old 7eba4505394e 3a127a31 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce INFO: task hung in linkwatch_event
2022/11/14 18:25 net-next-old ab00af85d2f8 943f4cb8 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce INFO: task hung in linkwatch_event
2022/11/13 13:49 net-next-old b548b17a93fd 3ead01ad .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce INFO: task hung in linkwatch_event
2022/11/12 17:25 net-next-old b548b17a93fd 3ead01ad .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce INFO: task hung in linkwatch_event
2022/11/12 06:04 net-next-old 2cf7e87fc459 3ead01ad .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce INFO: task hung in linkwatch_event
2022/05/13 15:58 net-next-old b67fd3d9d942 107f6434 .config console log report info ci-upstream-net-kasan-gce INFO: task hung in linkwatch_event
2023/05/19 18:07 https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git usb-testing ee4d21aa4a22 96689200 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-usb INFO: task hung in linkwatch_event
2023/04/21 05:58 linux-next 44bf136283e5 2b32bd34 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in linkwatch_event
2023/02/18 04:30 linux-next c068f40300a0 3e7039f4 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in linkwatch_event
2022/11/24 07:27 linux-next 15f3bff12cf6 12c66417 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in linkwatch_event
2022/11/23 10:12 linux-next 15f3bff12cf6 75740b3f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in linkwatch_event
2022/11/16 21:35 linux-next 15f3bff12cf6 3a127a31 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in linkwatch_event
2022/11/16 05:12 linux-next 3c1f24109dfc 3a127a31 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in linkwatch_event
2022/11/15 10:44 linux-next 5c92ddca1053 97de9cfc .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in linkwatch_event
2022/11/15 05:18 linux-next 5c92ddca1053 943f4cb8 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in linkwatch_event
2022/11/15 04:13 linux-next 5c92ddca1053 943f4cb8 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in linkwatch_event
2022/11/14 15:46 linux-next 5c92ddca1053 943f4cb8 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in linkwatch_event
* Struck through repros no longer work on HEAD.