syzbot


INFO: task hung in __tun_chr_ioctl (6)

Status: upstream: reported on 2024/06/07 06:03
Subsystems: net
[Documentation on labels]
Reported-by: syzbot+26c7b4c3afe5450b3e15@syzkaller.appspotmail.com
First crash: 266d, last: 6d11h
Discussions (2)
Title Replies (including bot) Last reply
[syzbot] Monthly wireguard report (Jul 2024) 0 (1) 2024/07/04 07:49
[syzbot] [net?] INFO: task hung in __tun_chr_ioctl (6) 0 (1) 2024/06/07 06:03
Similar bugs (7)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-6.1 INFO: task hung in __tun_chr_ioctl 8 239d 265d 0/3 auto-obsoleted due to no activity on 2024/09/25 13:24
upstream INFO: task hung in __tun_chr_ioctl (4) net 1 678d 678d 0/28 auto-obsoleted due to no activity on 2023/07/04 14:00
upstream INFO: task hung in __tun_chr_ioctl net 2 2289d 2521d 0/28 closed as dup on 2018/03/19 06:35
linux-5.15 INFO: task hung in __tun_chr_ioctl 2 230d 250d 0/3 auto-obsoleted due to no activity on 2024/10/03 23:39
upstream INFO: task hung in __tun_chr_ioctl (5) net 1 383d 383d 0/28 auto-obsoleted due to no activity on 2024/04/24 22:34
upstream INFO: task hung in __tun_chr_ioctl (3) net 2 870d 958d 0/28 auto-obsoleted due to no activity on 2023/01/03 09:42
upstream INFO: task hung in __tun_chr_ioctl (2) wireguard 1 1322d 1322d 0/28 auto-closed as invalid on 2021/09/27 23:09

Sample crash report:
INFO: task syz.8.2652:20377 blocked for more than 146 seconds.
      Not tainted 6.14.0-rc1-syzkaller-00028-g5c8c229261f1 #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz.8.2652      state:D stack:27392 pid:20377 tgid:20373 ppid:12610  task_flags:0x400040 flags:0x00000004
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5377 [inline]
 __schedule+0x190e/0x4c90 kernel/sched/core.c:6764
 __schedule_loop kernel/sched/core.c:6841 [inline]
 schedule+0x14b/0x320 kernel/sched/core.c:6856
 schedule_preempt_disabled+0x13/0x30 kernel/sched/core.c:6913
 __mutex_lock_common kernel/locking/mutex.c:662 [inline]
 __mutex_lock+0x817/0x1010 kernel/locking/mutex.c:730
 __tun_chr_ioctl+0x48c/0x2400 drivers/net/tun.c:3125
 vfs_ioctl fs/ioctl.c:51 [inline]
 __do_sys_ioctl fs/ioctl.c:906 [inline]
 __se_sys_ioctl+0xf7/0x170 fs/ioctl.c:892
 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:0x7f17c058cde9
RSP: 002b:00007f17be3f6038 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007f17c07a6080 RCX: 00007f17c058cde9
RDX: 00002000000003c0 RSI: 00000000800454d2 RDI: 0000000000000008
RBP: 00007f17c060e2a0 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000000 R14: 00007f17c07a6080 R15: 00007ffcabad6b18
 </TASK>

Showing all locks held in the system:
1 lock held by khungtaskd/30:
 #0: ffffffff8e9387e0 (rcu_read_lock){....}-{1:3}, at: rcu_lock_acquire include/linux/rcupdate.h:337 [inline]
 #0: ffffffff8e9387e0 (rcu_read_lock){....}-{1:3}, at: rcu_read_lock include/linux/rcupdate.h:849 [inline]
 #0: ffffffff8e9387e0 (rcu_read_lock){....}-{1:3}, at: debug_show_all_locks+0x55/0x2a0 kernel/locking/lockdep.c:6746
3 locks held by kworker/1:1/47:
 #0: ffff88801ac79d48 ((wq_completion)events_power_efficient){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3211 [inline]
 #0: ffff88801ac79d48 ((wq_completion)events_power_efficient){+.+.}-{0:0}, at: process_scheduled_works+0x93b/0x1840 kernel/workqueue.c:3317
 #1: ffffc90000b77c60 ((reg_check_chans).work){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3212 [inline]
 #1: ffffc90000b77c60 ((reg_check_chans).work){+.+.}-{0:0}, at: process_scheduled_works+0x976/0x1840 kernel/workqueue.c:3317
 #2: ffffffff8fcc0148 (rtnl_mutex){+.+.}-{4:4}, at: reg_check_chans_work+0x99/0xfb0 net/wireless/reg.c:2480
3 locks held by kworker/0:2/968:
 #0: ffff88801ac78d48 ((wq_completion)events){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3211 [inline]
 #0: ffff88801ac78d48 ((wq_completion)events){+.+.}-{0:0}, at: process_scheduled_works+0x93b/0x1840 kernel/workqueue.c:3317
 #1: ffffc90003e4fc60 (free_ipc_work){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3212 [inline]
 #1: ffffc90003e4fc60 (free_ipc_work){+.+.}-{0:0}, at: process_scheduled_works+0x976/0x1840 kernel/workqueue.c:3317
 #2: ffffffff8e93dcb8 (rcu_state.exp_mutex){+.+.}-{4:4}, at: exp_funnel_lock kernel/rcu/tree_exp.h:334 [inline]
 #2: ffffffff8e93dcb8 (rcu_state.exp_mutex){+.+.}-{4:4}, at: synchronize_rcu_expedited+0x451/0x830 kernel/rcu/tree_exp.h:996
3 locks held by kworker/R-ipv6_/3161:
 #0: ffff88802fec3148 ((wq_completion)ipv6_addrconf){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3211 [inline]
 #0: ffff88802fec3148 ((wq_completion)ipv6_addrconf){+.+.}-{0:0}, at: process_scheduled_works+0x93b/0x1840 kernel/workqueue.c:3317
 #1: ffffc9000cac7be0 ((work_completion)(&(&net->ipv6.addr_chk_work)->work)){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3212 [inline]
 #1: ffffc9000cac7be0 ((work_completion)(&(&net->ipv6.addr_chk_work)->work)){+.+.}-{0:0}, at: process_scheduled_works+0x976/0x1840 kernel/workqueue.c:3317
 #2: ffffffff8fcc0148 (rtnl_mutex){+.+.}-{4:4}, at: rtnl_net_lock include/linux/rtnetlink.h:129 [inline]
 #2: ffffffff8fcc0148 (rtnl_mutex){+.+.}-{4:4}, at: addrconf_verify_work+0x19/0x30 net/ipv6/addrconf.c:4730
3 locks held by kworker/u8:6/3514:
1 lock held by syslogd/5184:
3 locks held by udevd/5202:
1 lock held by dhcpcd/5495:
2 locks held by dhcpcd/5496:
2 locks held by getty/5591:
 #0: ffff8880275e60a0 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x25/0x70 drivers/tty/tty_ldisc.c:243
 #1: ffffc90002fde2f0 (&ldata->atomic_read_lock){+.+.}-{4:4}, at: n_tty_read+0x6a6/0x1e00 drivers/tty/n_tty.c:2211
2 locks held by syz-executor/5818:
1 lock held by syz-executor/10716:
3 locks held by kworker/0:7/10802:
 #0: ffff88801ac78d48 ((wq_completion)events){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3211 [inline]
 #0: ffff88801ac78d48 ((wq_completion)events){+.+.}-{0:0}, at: process_scheduled_works+0x93b/0x1840 kernel/workqueue.c:3317
 #1: ffffc90002f37c60 (deferred_process_work){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3212 [inline]
 #1: ffffc90002f37c60 (deferred_process_work){+.+.}-{0:0}, at: process_scheduled_works+0x976/0x1840 kernel/workqueue.c:3317
 #2: ffffffff8fcc0148 (rtnl_mutex){+.+.}-{4:4}, at: switchdev_deferred_process_work+0xe/0x20 net/switchdev/switchdev.c:104
2 locks held by syz-executor/14760:
2 locks held by syz-executor/14835:
 #0: ffff88805d8bcd80 (&hdev->req_lock){+.+.}-{4:4}, at: hci_dev_do_close net/bluetooth/hci_core.c:480 [inline]
 #0: ffff88805d8bcd80 (&hdev->req_lock){+.+.}-{4:4}, at: hci_unregister_dev+0x203/0x510 net/bluetooth/hci_core.c:2677
 #1: ffff88805d8bc078 (&hdev->lock){+.+.}-{4:4}, at: hci_dev_close_sync+0x5c8/0x11c0 net/bluetooth/hci_sync.c:5185
2 locks held by kworker/0:1/17355:
2 locks held by syz.1.2645/20358:
 #0: ffffffff8fcc0148 (rtnl_mutex){+.+.}-{4:4}, at: tun_detach drivers/net/tun.c:702 [inline]
 #0: ffffffff8fcc0148 (rtnl_mutex){+.+.}-{4:4}, at: tun_chr_close+0x3b/0x1b0 drivers/net/tun.c:3521
 #1: ffffffff8e93dcb8 (rcu_state.exp_mutex){+.+.}-{4:4}, at: exp_funnel_lock kernel/rcu/tree_exp.h:334 [inline]
 #1: ffffffff8e93dcb8 (rcu_state.exp_mutex){+.+.}-{4:4}, at: synchronize_rcu_expedited+0x451/0x830 kernel/rcu/tree_exp.h:996
5 locks held by syz-executor/20368:
1 lock held by syz.8.2652/20377:
 #0: ffffffff8fcc0148 (rtnl_mutex){+.+.}-{4:4}, at: __tun_chr_ioctl+0x48c/0x2400 drivers/net/tun.c:3125
1 lock held by syz-executor/20384:
1 lock held by syz-executor/20389:

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

NMI backtrace for cpu 0
CPU: 0 UID: 0 PID: 30 Comm: khungtaskd Not tainted 6.14.0-rc1-syzkaller-00028-g5c8c229261f1 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 12/27/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:236 [inline]
 watchdog+0x1058/0x10a0 kernel/hung_task.c:399
 kthread+0x7ab/0x920 kernel/kthread.c:464
 ret_from_fork+0x4d/0x80 arch/x86/kernel/process.c:148
 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: 3514 Comm: kworker/u8:6 Not tainted 6.14.0-rc1-syzkaller-00028-g5c8c229261f1 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 12/27/2024
Workqueue: events_unbound nsim_dev_trap_report_work
RIP: 0010:poison_slab_object mm/kasan/common.c:247 [inline]
RIP: 0010:__kasan_slab_free+0x51/0x70 mm/kasan/common.c:264
Code: 5b 41 5e e9 6c 7f ea fe 84 c9 75 26 41 8b 76 1c ff ce 83 ce 07 ff c6 0f b6 ca 48 89 df ba fb 00 00 00 e8 02 39 00 00 4c 89 f7 <48> 89 de e8 37 2d 00 00 4c 89 f7 48 89 de 5b 41 5e e9 09 41 00 00
RSP: 0018:ffffc9000cdf7928 EFLAGS: 00000207
RAX: ffffed10143e3000 RBX: ffff8880a1f18000 RCX: 0000000000000000
RDX: 0000000000000200 RSI: 00000000000000fb RDI: ffff88801ac42140
RBP: 0000000000000000 R08: dffffc0000000000 R09: ffffed10143e3000
R10: dffffc0000000000 R11: fffffbfff285f328 R12: ffff88801ac42140
R13: ffff8880a1f18000 R14: ffff88801ac42140 R15: ffffea000287c600
FS:  0000000000000000(0000) GS:ffff8880b8700000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000200000e23030 CR3: 00000000a3d6e000 CR4: 0000000000350ef0
Call Trace:
 <NMI>
 </NMI>
 <TASK>
 kasan_slab_free include/linux/kasan.h:233 [inline]
 slab_free_hook mm/slub.c:2353 [inline]
 slab_free mm/slub.c:4609 [inline]
 kfree+0x196/0x430 mm/slub.c:4757
 skb_kfree_head net/core/skbuff.c:1086 [inline]
 skb_free_head net/core/skbuff.c:1098 [inline]
 skb_release_data+0x6a0/0x8a0 net/core/skbuff.c:1125
 skb_release_all net/core/skbuff.c:1190 [inline]
 __kfree_skb net/core/skbuff.c:1204 [inline]
 consume_skb+0x9f/0xf0 net/core/skbuff.c:1436
 nsim_dev_trap_report drivers/net/netdevsim/dev.c:821 [inline]
 nsim_dev_trap_report_work+0x7cc/0xb50 drivers/net/netdevsim/dev.c:851
 process_one_work kernel/workqueue.c:3236 [inline]
 process_scheduled_works+0xa68/0x1840 kernel/workqueue.c:3317
 worker_thread+0x870/0xd30 kernel/workqueue.c:3398
 kthread+0x7ab/0x920 kernel/kthread.c:464
 ret_from_fork+0x4d/0x80 arch/x86/kernel/process.c:148
 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244
 </TASK>

Crashes (76):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2025/02/05 11:29 upstream 5c8c229261f1 5896748e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in __tun_chr_ioctl
2025/01/22 13:34 upstream 62de6e168526 da72ac06 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in __tun_chr_ioctl
2024/12/14 08:22 upstream f932fb9b4074 7cbfbb3a .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root INFO: task hung in __tun_chr_ioctl
2024/09/29 19:58 upstream e7ed34365879 ba29ff75 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root INFO: task hung in __tun_chr_ioctl
2024/09/27 22:26 upstream e477dba5442c 2b1784d6 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root INFO: task hung in __tun_chr_ioctl
2024/09/24 16:10 upstream abf2050f51fd 5643e0e9 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in __tun_chr_ioctl
2024/07/22 13:24 upstream 933069701c1b f063dfd9 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root INFO: task hung in __tun_chr_ioctl
2024/07/06 00:06 upstream d270dd21bee0 2a40360c .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in __tun_chr_ioctl
2024/07/01 10:13 upstream 22a40d14b572 b294e901 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in __tun_chr_ioctl
2024/06/20 21:05 upstream 2ccbdf43d5e7 dac2aa43 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in __tun_chr_ioctl
2024/06/20 19:35 upstream 2ccbdf43d5e7 dac2aa43 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root INFO: task hung in __tun_chr_ioctl
2024/06/16 19:35 upstream 2ccbdf43d5e7 f429ab00 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in __tun_chr_ioctl
2024/06/16 15:01 upstream 2ccbdf43d5e7 f429ab00 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in __tun_chr_ioctl
2024/06/16 07:31 upstream 2ccbdf43d5e7 f429ab00 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in __tun_chr_ioctl
2024/06/10 06:47 upstream 83a7eefedc9b 82c05ab8 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root INFO: task hung in __tun_chr_ioctl
2024/06/08 17:09 upstream dc772f8237f9 82c05ab8 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root INFO: task hung in __tun_chr_ioctl
2024/06/05 22:08 upstream 71d7b52cc33b 121701b6 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root INFO: task hung in __tun_chr_ioctl
2024/06/04 18:21 upstream 2ab795141095 a1feae05 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in __tun_chr_ioctl
2024/06/04 18:18 upstream 2ab795141095 a1feae05 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in __tun_chr_ioctl
2024/06/04 15:53 upstream 2ab795141095 a1feae05 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in __tun_chr_ioctl
2024/06/04 01:28 upstream f06ce441457d 0aba2352 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root INFO: task hung in __tun_chr_ioctl
2024/06/01 14:06 upstream cc8ed4d0a848 3113787f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root INFO: task hung in __tun_chr_ioctl
2024/06/01 03:19 upstream d8ec19857b09 3113787f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root INFO: task hung in __tun_chr_ioctl
2024/05/31 13:20 upstream 4a4be1ad3a6e 34889ee3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in __tun_chr_ioctl
2024/05/31 10:13 upstream 4a4be1ad3a6e 34889ee3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root INFO: task hung in __tun_chr_ioctl
2024/05/31 03:08 upstream 4a4be1ad3a6e 34889ee3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root INFO: task hung in __tun_chr_ioctl
2024/05/28 21:23 upstream e0cce98fe279 34889ee3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in __tun_chr_ioctl
2024/05/28 19:03 upstream e0cce98fe279 34889ee3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root INFO: task hung in __tun_chr_ioctl
2024/05/28 08:48 upstream 2bfcfd584ff5 f550015e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root INFO: task hung in __tun_chr_ioctl
2024/05/25 18:41 upstream 56fb6f92854f a10a183e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root INFO: task hung in __tun_chr_ioctl
2024/05/25 18:39 upstream 56fb6f92854f a10a183e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root INFO: task hung in __tun_chr_ioctl
2024/05/20 23:31 upstream eb6a9339efeb c0f1611a .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in __tun_chr_ioctl
2024/10/04 17:05 upstream 0c559323bbaa d7906eff .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-386 INFO: task hung in __tun_chr_ioctl
2024/10/02 23:09 upstream e32cde8d2bd7 a4c7fd36 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-386 INFO: task hung in __tun_chr_ioctl
2024/09/20 06:29 upstream 2004cef11ea0 6f888b75 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-386 INFO: task hung in __tun_chr_ioctl
2024/11/08 15:24 net 55d42a0c3f9c 179b040e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce INFO: task hung in __tun_chr_ioctl
2024/10/17 06:10 net 11d06f0aaef8 666f77ed .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce INFO: task hung in __tun_chr_ioctl
2024/10/12 15:29 net 174714f0e505 084d8178 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce INFO: task hung in __tun_chr_ioctl
2024/10/08 06:31 net 631083143315 402f1df0 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce INFO: task hung in __tun_chr_ioctl
2024/06/16 22:56 net be27b8965297 f429ab00 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce INFO: task hung in __tun_chr_ioctl
2024/06/10 20:19 net 5add2f728846 048c640a .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce INFO: task hung in __tun_chr_ioctl
2024/06/10 13:00 net 5add2f728846 82c05ab8 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce INFO: task hung in __tun_chr_ioctl
2024/06/01 16:33 net d8ec19857b09 3113787f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce INFO: task hung in __tun_chr_ioctl
2024/05/27 22:17 net 52a2f0608366 f550015e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce INFO: task hung in __tun_chr_ioctl
2024/05/26 17:17 net 0b4f5add9fa5 a10a183e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce INFO: task hung in __tun_chr_ioctl
2024/05/25 15:54 net 0b4f5add9fa5 a10a183e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce INFO: task hung in __tun_chr_ioctl
2024/05/25 02:58 net 0b4f5add9fa5 a10a183e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce INFO: task hung in __tun_chr_ioctl
2024/05/22 18:10 net 30a92c9e3d6b 4d098039 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce INFO: task hung in __tun_chr_ioctl
2024/10/09 10:28 net-next 36efaca9cb28 402f1df0 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce INFO: task hung in __tun_chr_ioctl
2024/06/19 20:10 net-next 3ec8d7572a69 41b7e219 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce INFO: task hung in __tun_chr_ioctl
2024/06/10 11:49 net-next 28f961f9d5b7 82c05ab8 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce INFO: task hung in __tun_chr_ioctl
2024/06/10 09:22 net-next 28f961f9d5b7 82c05ab8 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce INFO: task hung in __tun_chr_ioctl
2024/06/08 10:05 net-next a99997323654 82c05ab8 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce INFO: task hung in __tun_chr_ioctl
2024/06/03 20:59 net-next 93e30878f7ec 0aba2352 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce INFO: task hung in __tun_chr_ioctl
2024/06/03 07:07 net-next b5c089880723 3113787f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce INFO: task hung in __tun_chr_ioctl
2024/06/03 05:58 net-next b5c089880723 3113787f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce INFO: task hung in __tun_chr_ioctl
2024/05/28 20:18 net-next c30ff5f3aec3 34889ee3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce INFO: task hung in __tun_chr_ioctl
2024/05/28 10:31 net-next 5233a55a5254 f550015e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce INFO: task hung in __tun_chr_ioctl
2024/05/28 02:43 net-next 5233a55a5254 f550015e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce INFO: task hung in __tun_chr_ioctl
2024/05/27 08:09 net-next 66ad4829ddd0 a10a183e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce INFO: task hung in __tun_chr_ioctl
2024/05/21 07:09 net-next 4b377b4868ef c0f1611a .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce INFO: task hung in __tun_chr_ioctl
2024/05/21 03:45 net-next 4b377b4868ef c0f1611a .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce INFO: task hung in __tun_chr_ioctl
2024/05/21 01:02 net-next 4b377b4868ef c0f1611a .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce INFO: task hung in __tun_chr_ioctl
2024/10/11 07:24 linux-next 0cca97bf2364 cd942402 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in __tun_chr_ioctl
2024/05/31 09:44 linux-next 0e1980c40b6e 34889ee3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in __tun_chr_ioctl
2024/05/28 22:42 linux-next 6dc544b66971 34889ee3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in __tun_chr_ioctl
2024/05/28 22:38 linux-next 6dc544b66971 34889ee3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in __tun_chr_ioctl
2024/05/28 22:38 linux-next 6dc544b66971 34889ee3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in __tun_chr_ioctl
2024/05/28 10:34 linux-next 6dc544b66971 f550015e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in __tun_chr_ioctl
* Struck through repros no longer work on HEAD.