syzbot


INFO: task hung in tun_chr_close (5)

Status: upstream: reported syz repro on 2024/09/15 19:59
Subsystems: net
[Documentation on labels]
Reported-by: syzbot+b0ae8f1abf7d891e0426@syzkaller.appspotmail.com
First crash: 403d, last: 3d02h
Cause bisection: introduced by (bisect log) :
commit 5a781ccbd19e4664babcbe4b4ead7aa2b9283d22
Author: Vinicius Costa Gomes <vinicius.gomes@intel.com>
Date: Sat Sep 29 00:59:43 2018 +0000

  tc: Add support for configuring the taprio scheduler

Crash: BUG: unable to handle kernel NULL pointer dereference in taprio_dequeue (log)
Repro: syz .config
  
Discussions (1)
Title Replies (including bot) Last reply
[syzbot] [wireguard?] INFO: task hung in tun_chr_close (5) 0 (3) 2025/01/05 15:45
Similar bugs (13)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-5.15 INFO: task hung in tun_chr_close 1 40 275d 517d 0/3 auto-obsoleted due to no activity on 2025/02/09 21:18
linux-4.19 INFO: task hung in tun_chr_close 1 1 1832d 1832d 0/1 auto-closed as invalid on 2020/12/09 18:55
upstream INFO: task hung in tun_chr_close (4) net 1 syz unreliable error 14 1373d 1434d 0/29 auto-closed as invalid on 2022/09/18 21:51
upstream INFO: task hung in tun_chr_close net 1 5 2158d 2739d 0/29 closed as dup on 2018/02/16 08:24
linux-4.19 INFO: task hung in tun_chr_close (3) 1 1 1109d 1109d 0/1 auto-obsoleted due to no activity on 2022/12/03 04:48
linux-6.1 INFO: task hung in tun_chr_close 1 31 387d 454d 0/3 auto-obsoleted due to no activity on 2024/10/04 23:47
upstream INFO: task hung in rtnetlink_rcv_msg net 1 C inconclusive inconclusive 1970 405d 2368d 26/29 fixed on 2024/07/09 19:14
android-49 INFO: task hung in tun_chr_close 1 1 2654d 2654d 0/3 auto-closed as invalid on 2019/02/22 14:33
linux-4.19 INFO: task hung in tun_chr_close (4) 1 3 915d 942d 0/1 upstream: reported on 2023/01/18 07:05
linux-4.19 INFO: task hung in tun_chr_close (2) 1 6 1321d 1415d 0/1 auto-closed as invalid on 2022/05/04 09:03
upstream INFO: task hung in tun_chr_close (3) net 1 1 1545d 1545d 0/29 auto-closed as invalid on 2021/08/23 13:06
android-44 INFO: task hung in tun_chr_close 1 1 2663d 2663d 0/2 auto-closed as invalid on 2019/02/22 15:23
upstream INFO: task hung in tun_chr_close (2) net 1 7 1654d 1875d 0/29 auto-closed as invalid on 2021/05/17 11:47
Last patch testing requests (10)
Created Duration User Patch Repo Result
2025/07/30 16:11 31m retest repro net report log
2025/07/30 14:31 19m retest repro upstream report log
2025/07/30 07:13 20m retest repro upstream OK log
2025/07/30 07:13 18m retest repro upstream report log
2025/07/30 07:13 19m retest repro upstream report log
2025/05/21 13:46 20m retest repro upstream report log
2025/04/18 23:22 20m retest repro net report log
2025/04/04 10:07 17m retest repro upstream report log
2025/04/04 10:07 20m retest repro upstream report log
2025/04/04 10:07 19m retest repro upstream report log

Sample crash report:
INFO: task syz.0.25:5768 blocked for more than 145 seconds.
      Not tainted 6.16.0-syzkaller-12063-g37816488247d #0
      Blocked by coredump.
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz.0.25        state:D stack:26888 pid:5768  tgid:5767  ppid:5505   task_flags:0x40054c flags:0x00004002
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5357 [inline]
 __schedule+0x1798/0x4cc0 kernel/sched/core.c:6961
 __schedule_loop kernel/sched/core.c:7043 [inline]
 schedule+0x165/0x360 kernel/sched/core.c:7058
 schedule_preempt_disabled+0x13/0x30 kernel/sched/core.c:7115
 __mutex_lock_common kernel/locking/mutex.c:676 [inline]
 __mutex_lock+0x7e6/0x1360 kernel/locking/mutex.c:760
 tun_detach drivers/net/tun.c:634 [inline]
 tun_chr_close+0x3e/0x1c0 drivers/net/tun.c:3433
 __fput+0x44c/0xa70 fs/file_table.c:468
 task_work_run+0x1d4/0x260 kernel/task_work.c:227
 exit_task_work include/linux/task_work.h:40 [inline]
 do_exit+0x6b5/0x2300 kernel/exit.c:961
 do_group_exit+0x21c/0x2d0 kernel/exit.c:1102
 get_signal+0x1286/0x1340 kernel/signal.c:3034
 arch_do_signal_or_restart+0x9a/0x750 arch/x86/kernel/signal.c:337
 exit_to_user_mode_loop+0x75/0x110 kernel/entry/common.c:40
 exit_to_user_mode_prepare include/linux/irq-entry-common.h:225 [inline]
 syscall_exit_to_user_mode_work include/linux/entry-common.h:175 [inline]
 syscall_exit_to_user_mode include/linux/entry-common.h:210 [inline]
 do_syscall_64+0x2bd/0x3b0 arch/x86/entry/syscall_64.c:100
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f88ec18ebe9
RSP: 002b:00007f88ecfe7038 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: fffffffffffffff0 RBX: 00007f88ec3b5fa0 RCX: 00007f88ec18ebe9
RDX: 0000200000000000 RSI: 00000000000089a2 RDI: 0000000000000003
RBP: 00007f88ec211e19 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f88ec3b6038 R14: 00007f88ec3b5fa0 R15: 00007fff101c4de8
 </TASK>

Showing all locks held in the system:
4 locks held by kworker/0:0/9:
2 locks held by kworker/0:1/10:
3 locks held by kworker/u4:0/12:
3 locks held by kworker/u4:1/13:
1 lock held by khungtaskd/26:
 #0: ffffffff8e139ee0 (rcu_read_lock){....}-{1:3}, at: rcu_lock_acquire include/linux/rcupdate.h:331 [inline]
 #0: ffffffff8e139ee0 (rcu_read_lock){....}-{1:3}, at: rcu_read_lock include/linux/rcupdate.h:841 [inline]
 #0: ffffffff8e139ee0 (rcu_read_lock){....}-{1:3}, at: debug_show_all_locks+0x2e/0x180 kernel/locking/lockdep.c:6775
3 locks held by kworker/u4:2/31:
2 locks held by kworker/u4:3/38:
4 locks held by kworker/u4:4/64:
3 locks held by kworker/0:2/795:
4 locks held by kworker/u4:5/1037:
3 locks held by kworker/u4:6/1040:
 #0: ffff88803eb4a948 ((wq_completion)ipv6_addrconf){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3211 [inline]
 #0: ffff88803eb4a948 ((wq_completion)ipv6_addrconf){+.+.}-{0:0}, at: process_scheduled_works+0x9b4/0x17b0 kernel/workqueue.c:3319
 #1: ffffc9000277fbc0 ((work_completion)(&(&ifa->dad_work)->work)){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3212 [inline]
 #1: ffffc9000277fbc0 ((work_completion)(&(&ifa->dad_work)->work)){+.+.}-{0:0}, at: process_scheduled_works+0x9ef/0x17b0 kernel/workqueue.c:3319
 #2: ffffffff8f536888 (rtnl_mutex){+.+.}-{4:4}, at: rtnl_net_lock include/linux/rtnetlink.h:130 [inline]
 #2: ffffffff8f536888 (rtnl_mutex){+.+.}-{4:4}, at: addrconf_dad_work+0x112/0x14b0 net/ipv6/addrconf.c:4194
3 locks held by kworker/u4:7/1041:
4 locks held by kworker/u4:8/1045:
3 locks held by kworker/u4:10/1154:
2 locks held by kworker/0:3/1353:
1 lock held by udevd/4756:
1 lock held by dhcpcd/5052:
 #0: ffffffff8f536888 (rtnl_mutex){+.+.}-{4:4}, at: rtnl_net_lock include/linux/rtnetlink.h:130 [inline]
 #0: ffffffff8f536888 (rtnl_mutex){+.+.}-{4:4}, at: inet6_rtm_newaddr+0x5b7/0xd20 net/ipv6/addrconf.c:5027
2 locks held by getty/5146:
 #0: ffff8880372ed0a0 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x25/0x70 drivers/tty/tty_ldisc.c:243
 #1: ffffc9000018e2f0 (&ldata->atomic_read_lock){+.+.}-{4:4}, at: n_tty_read+0x43e/0x1400 drivers/tty/n_tty.c:2222
3 locks held by syz-execprog/5386:
2 locks held by kworker/0:4/5497:
1 lock held by syz-executor/5503:
 #0: ffffffff8f536888 (rtnl_mutex){+.+.}-{4:4}, at: tun_detach drivers/net/tun.c:634 [inline]
 #0: ffffffff8f536888 (rtnl_mutex){+.+.}-{4:4}, at: tun_chr_close+0x3e/0x1c0 drivers/net/tun.c:3433
5 locks held by kworker/u5:3/5509:
 #0: ffff888059ee2148 ((wq_completion)hci7){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3211 [inline]
 #0: ffff888059ee2148 ((wq_completion)hci7){+.+.}-{0:0}, at: process_scheduled_works+0x9b4/0x17b0 kernel/workqueue.c:3319
 #1: ffffc9000292fbc0 ((work_completion)(&hdev->cmd_sync_work)){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3212 [inline]
 #1: ffffc9000292fbc0 ((work_completion)(&hdev->cmd_sync_work)){+.+.}-{0:0}, at: process_scheduled_works+0x9ef/0x17b0 kernel/workqueue.c:3319
 #2: ffff8880448a4dc0 (&hdev->req_lock){+.+.}-{4:4}, at: hci_cmd_sync_work+0x1d4/0x3a0 net/bluetooth/hci_sync.c:331
 #3: ffff8880448a40b8 (&hdev->lock){+.+.}-{4:4}, at: hci_abort_conn_sync+0x242/0xe30 net/bluetooth/hci_sync.c:5670
 #4: ffffffff8e13f978 (rcu_state.exp_mutex){+.+.}-{4:4}, at: exp_funnel_lock kernel/rcu/tree_exp.h:311 [inline]
 #4: ffffffff8e13f978 (rcu_state.exp_mutex){+.+.}-{4:4}, at: synchronize_rcu_expedited+0x2f6/0x730 kernel/rcu/tree_exp.h:957
1 lock held by syz-executor/5510:
 #0: ffffffff8f536888 (rtnl_mutex){+.+.}-{4:4}, at: tun_detach drivers/net/tun.c:634 [inline]
 #0: ffffffff8f536888 (rtnl_mutex){+.+.}-{4:4}, at: tun_chr_close+0x3e/0x1c0 drivers/net/tun.c:3433
1 lock held by syz-executor/5512:
 #0: ffffffff8f536888 (rtnl_mutex){+.+.}-{4:4}, at: tun_detach drivers/net/tun.c:634 [inline]
 #0: ffffffff8f536888 (rtnl_mutex){+.+.}-{4:4}, at: tun_chr_close+0x3e/0x1c0 drivers/net/tun.c:3433
1 lock held by syz-executor/5515:
 #0: ffffffff8f536888 (rtnl_mutex){+.+.}-{4:4}, at: tun_detach drivers/net/tun.c:634 [inline]
 #0: ffffffff8f536888 (rtnl_mutex){+.+.}-{4:4}, at: tun_chr_close+0x3e/0x1c0 drivers/net/tun.c:3433
1 lock held by syz-executor/5517:
 #0: ffffffff8f536888 (rtnl_mutex){+.+.}-{4:4}, at: tun_detach drivers/net/tun.c:634 [inline]
 #0: ffffffff8f536888 (rtnl_mutex){+.+.}-{4:4}, at: tun_chr_close+0x3e/0x1c0 drivers/net/tun.c:3433
4 locks held by kworker/0:5/5642:
2 locks held by kworker/0:6/5666:
2 locks held by kworker/u4:12/5759:
3 locks held by kworker/u4:15/5763:
4 locks held by kworker/u4:16/5766:
1 lock held by syz.0.25/5768:
 #0: ffffffff8f536888 (rtnl_mutex){+.+.}-{4:4}, at: tun_detach drivers/net/tun.c:634 [inline]
 #0: ffffffff8f536888 (rtnl_mutex){+.+.}-{4:4}, at: tun_chr_close+0x3e/0x1c0 drivers/net/tun.c:3433
2 locks held by kworker/0:9/5769:
2 locks held by kworker/0:10/5770:
3 locks held by kworker/0:11/5771:
4 locks held by kworker/0:12/5772:
 #0: ffff88801a4d4148 ((wq_completion)events_power_efficient){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3211 [inline]
 #0: ffff88801a4d4148 ((wq_completion)events_power_efficient){+.+.}-{0:0}, at: process_scheduled_works+0x9b4/0x17b0 kernel/workqueue.c:3319
 #1: ffffc9000d64fbc0 ((reg_check_chans).work){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3212 [inline]
 #1: ffffc9000d64fbc0 ((reg_check_chans).work){+.+.}-{0:0}, at: process_scheduled_works+0x9ef/0x17b0 kernel/workqueue.c:3319
 #2: ffffffff8f536888 (rtnl_mutex){+.+.}-{4:4}, at: reg_check_chans_work+0x95/0xf30 net/wireless/reg.c:2483
 #3: ffff888043c88768 (&rdev->wiphy.mtx){+.+.}-{4:4}, at: class_wiphy_constructor include/net/cfg80211.h:6212 [inline]
 #3: ffff888043c88768 (&rdev->wiphy.mtx){+.+.}-{4:4}, at: reg_leave_invalid_chans net/wireless/reg.c:2471 [inline]
 #3: ffff888043c88768 (&rdev->wiphy.mtx){+.+.}-{4:4}, at: reg_check_chans_work+0x164/0xf30 net/wireless/reg.c:2486
3 locks held by kworker/0:14/5775:
1 lock held by syz-executor/5777:
 #0: ffffffff8f536888 (rtnl_mutex){+.+.}-{4:4}, at: rtnl_net_lock include/linux/rtnetlink.h:130 [inline]
 #0: ffffffff8f536888 (rtnl_mutex){+.+.}-{4:4}, at: inet_rtm_newaddr+0x3b0/0x18b0 net/ipv4/devinet.c:979
1 lock held by syz-executor/5784:
 #0: ffffffff8f536888 (rtnl_mutex){+.+.}-{4:4}, at: rtnl_net_lock include/linux/rtnetlink.h:130 [inline]
 #0: ffffffff8f536888 (rtnl_mutex){+.+.}-{4:4}, at: inet_rtm_newaddr+0x3b0/0x18b0 net/ipv4/devinet.c:979
3 locks held by kworker/u4:17/5788:
1 lock held by syz-executor/5792:
 #0: ffffffff8f536888 (rtnl_mutex){+.+.}-{4:4}, at: rtnl_net_lock include/linux/rtnetlink.h:130 [inline]
 #0: ffffffff8f536888 (rtnl_mutex){+.+.}-{4:4}, at: inet_rtm_newaddr+0x3b0/0x18b0 net/ipv4/devinet.c:979
1 lock held by syz-executor/5795:
 #0: ffffffff8f536888 (rtnl_mutex){+.+.}-{4:4}, at: rtnl_net_lock include/linux/rtnetlink.h:130 [inline]
 #0: ffffffff8f536888 (rtnl_mutex){+.+.}-{4:4}, at: inet_rtm_newaddr+0x3b0/0x18b0 net/ipv4/devinet.c:979
1 lock held by syz-executor/5805:
 #0: ffffffff8f536888 (rtnl_mutex){+.+.}-{4:4}, at: rtnl_net_lock include/linux/rtnetlink.h:130 [inline]
 #0: ffffffff8f536888 (rtnl_mutex){+.+.}-{4:4}, at: inet_rtm_newaddr+0x3b0/0x18b0 net/ipv4/devinet.c:979
3 locks held by kworker/u4:18/5814:
3 locks held by kworker/u4:19/5815:
1 lock held by syz-executor/5824:
 #0: ffffffff8f536888 (rtnl_mutex){+.+.}-{4:4}, at: rtnl_net_lock include/linux/rtnetlink.h:130 [inline]
 #0: ffffffff8f536888 (rtnl_mutex){+.+.}-{4:4}, at: inet_rtm_newaddr+0x3b0/0x18b0 net/ipv4/devinet.c:979
1 lock held by syz-executor/5827:
 #0: ffffffff8f536888 (rtnl_mutex){+.+.}-{4:4}, at: rtnl_net_lock include/linux/rtnetlink.h:130 [inline]
 #0: ffffffff8f536888 (rtnl_mutex){+.+.}-{4:4}, at: inet_rtm_newaddr+0x3b0/0x18b0 net/ipv4/devinet.c:979
2 locks held by syz-executor/5838:
1 lock held by syz-executor/5842:
 #0: ffffffff8f536888 (rtnl_mutex){+.+.}-{4:4}, at: rtnl_net_lock include/linux/rtnetlink.h:130 [inline]
 #0: ffffffff8f536888 (rtnl_mutex){+.+.}-{4:4}, at: inet_rtm_newaddr+0x3b0/0x18b0 net/ipv4/devinet.c:979
1 lock held by syz-executor/5849:
 #0: ffffffff8f536888 (rtnl_mutex){+.+.}-{4:4}, at: rtnl_net_lock include/linux/rtnetlink.h:130 [inline]
 #0: ffffffff8f536888 (rtnl_mutex){+.+.}-{4:4}, at: inet_rtm_newaddr+0x3b0/0x18b0 net/ipv4/devinet.c:979
1 lock held by syz-executor/5851:
 #0: ffffffff8f536888 (rtnl_mutex){+.+.}-{4:4}, at: rtnl_net_lock include/linux/rtnetlink.h:130 [inline]
 #0: ffffffff8f536888 (rtnl_mutex){+.+.}-{4:4}, at: inet_rtm_newaddr+0x3b0/0x18b0 net/ipv4/devinet.c:979
4 locks held by kworker/0:18/5852:
4 locks held by kworker/u4:21/5860:
2 locks held by syz-executor/5874:
3 locks held by udevd/5878:
2 locks held by syz-executor/5879:

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

NMI backtrace for cpu 0
CPU: 0 UID: 0 PID: 26 Comm: khungtaskd Not tainted 6.16.0-syzkaller-12063-g37816488247d #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_lvl+0x189/0x250 lib/dump_stack.c:120
 nmi_cpu_backtrace+0x39e/0x3d0 lib/nmi_backtrace.c:113
 nmi_trigger_cpumask_backtrace+0x17a/0x300 lib/nmi_backtrace.c:62
 trigger_all_cpu_backtrace include/linux/nmi.h:160 [inline]
 check_hung_uninterruptible_tasks kernel/hung_task.c:328 [inline]
 watchdog+0xf93/0xfe0 kernel/hung_task.c:491
 kthread+0x70e/0x8a0 kernel/kthread.c:463
 ret_from_fork+0x3fc/0x770 arch/x86/kernel/process.c:148
 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245
 </TASK>

Crashes (597):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2025/08/09 04:06 upstream 37816488247d 32a0e5ed .config console log report syz / log [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root INFO: task hung in tun_chr_close
2025/08/05 18:13 upstream 7e161a991ea7 37880f40 .config console log report syz / log [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root INFO: task hung in tun_chr_close
2025/05/07 12:22 upstream 0d8d44db295c 350f4ffc .config console log report syz / log [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root INFO: task hung in tun_chr_close
2025/03/08 21:35 upstream 2a520073e74f 7e3bd60d .config console log report syz / log [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root INFO: task hung in tun_chr_close
2024/11/19 01:31 upstream 9fb2cfa4635a 571351cb .config console log report syz / log [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root INFO: task hung in tun_chr_close
2024/12/17 17:58 net 7ed2d9158877 c8c15bb2 .config console log report syz / log [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce INFO: task hung in tun_chr_close
2025/07/31 06:03 upstream e8d780dcd957 f8f2b4da .config console log report info [disk image] [vmlinux] [kernel image] ci-qemu-gce-upstream-auto INFO: task hung in tun_chr_close
2025/07/16 07:08 upstream 155a3c003e55 03fcfc4b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in tun_chr_close
2025/07/11 18:48 upstream 40f92e79b0aa 3cda49cf .config console log report info [disk image] [vmlinux] [kernel image] ci-qemu-gce-upstream-auto INFO: task hung in tun_chr_close
2025/07/02 08:02 upstream 66701750d556 ffe4b334 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root INFO: task hung in tun_chr_close
2025/06/26 09:14 upstream 92ca6c498a5e 26d77996 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in tun_chr_close
2025/05/29 16:46 upstream 90b83efa6701 3d2f584d .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root INFO: task hung in tun_chr_close
2025/04/27 10:16 upstream 5bc1018675ec c6b4fb39 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in tun_chr_close
2025/04/24 11:24 upstream a79be02bba5c 9c80ffa0 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in tun_chr_close
2025/04/21 21:00 upstream 9d7a0577c9db 2a20f901 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root INFO: task hung in tun_chr_close
2025/04/04 19:40 upstream e48e99b6edf4 1c4febdb .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root INFO: task hung in tun_chr_close
2025/03/10 06:00 upstream 80e54e84911a 163f510d .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in tun_chr_close
2025/03/09 06:08 upstream 2a520073e74f 163f510d .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in tun_chr_close
2025/02/25 22:52 upstream 2a1944bff549 d34966d1 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in tun_chr_close
2025/02/06 08:16 upstream 92514ef226f5 577d049b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in tun_chr_close
2025/01/19 16:50 upstream fda5e3f28400 f2cb035c .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root INFO: task hung in tun_chr_close
2025/01/19 10:09 upstream fda5e3f28400 f2cb035c .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root INFO: task hung in tun_chr_close
2025/01/13 12:54 upstream 5bc55a333a2f 6dbc6a9b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in tun_chr_close
2025/01/11 02:10 upstream e0daef7de1ac 67d7ec0a .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in tun_chr_close
2025/01/06 08:12 upstream ab75170520d4 f3558dbf .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root INFO: task hung in tun_chr_close
2025/01/04 01:11 upstream 0bc21e701a6f f3558dbf .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in tun_chr_close
2025/01/02 03:50 upstream 56e6a3499e14 d3ccff63 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in tun_chr_close
2024/09/11 19:42 upstream 7c6a3a65ace7 9326a104 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root INFO: task hung in tun_chr_close
2024/09/01 23:27 upstream c9f016e72b5c 1eda0d14 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root INFO: task hung in tun_chr_close
2024/10/17 00:04 upstream c964ced77262 666f77ed .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-386 INFO: task hung in tun_chr_close
2025/03/08 19:03 upstream 2a520073e74f 7e3bd60d .config console log report syz / log [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root INFO: task hung in tun_chr_close
2025/06/18 05:38 net 0aff00432cc7 e77fae15 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce INFO: task hung in tun_chr_close
2025/03/17 01:47 net 4003c9e78778 e2826670 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce INFO: task hung in tun_chr_close
2025/03/14 06:33 net 2409fa66e29a e2826670 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce INFO: task hung in tun_chr_close
2025/03/12 15:14 net d2b9d97e89c7 ee70e6db .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce INFO: task hung in tun_chr_close
2025/03/11 21:53 net 77b2ab31fc65 f2eee6b3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce INFO: task hung in tun_chr_close
2025/03/05 01:39 net 3c6a041b317a c3901742 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce INFO: task hung in tun_chr_close
2025/02/25 18:12 net bc50682128bd d34966d1 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce INFO: task hung in tun_chr_close
2025/02/24 08:44 net 28b04731a38c d34966d1 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce INFO: task hung in tun_chr_close
2025/02/16 19:49 net 071ed42cff4f 40a34ec9 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce INFO: task hung in tun_chr_close
2025/02/16 09:18 net 071ed42cff4f 40a34ec9 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce INFO: task hung in tun_chr_close
2025/02/07 13:18 net 1438f5d07b9a a4f327c2 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce INFO: task hung in tun_chr_close
2025/02/06 01:48 net a1300691aed9 577d049b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce INFO: task hung in tun_chr_close
2025/02/03 12:51 net 235174b2bed8 a21a8419 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce INFO: task hung in tun_chr_close
2025/01/29 23:44 net 9e6c4e6b605c afe4eff5 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce INFO: task hung in tun_chr_close
2025/01/28 05:39 net 05d91cdb1f91 18070896 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce INFO: task hung in tun_chr_close
2025/01/28 00:13 net 05d91cdb1f91 18070896 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce INFO: task hung in tun_chr_close
2025/01/25 14:29 net 15a901361ec3 9fbd772e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce INFO: task hung in tun_chr_close
2025/08/15 03:19 net-next 875c541ea680 dcc075fb .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce INFO: task hung in tun_chr_close
2025/08/09 11:19 net-next 37816488247d 32a0e5ed .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce INFO: task hung in tun_chr_close
2025/06/23 09:16 net-next 5e95c0a3a55a d6cdfb8a .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce INFO: task hung in tun_chr_close
2025/06/05 14:30 net-next 90b83efa6701 6b6b5f21 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce INFO: task hung in tun_chr_close
2025/03/21 07:35 net-next 6f13bec53a48 62330552 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce INFO: task hung in tun_chr_close
2025/03/21 05:32 net-next 6f13bec53a48 62330552 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce INFO: task hung in tun_chr_close
2025/03/15 09:40 net-next bfc6c67ec2d6 e2826670 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce INFO: task hung in tun_chr_close
2025/03/10 10:12 net-next 8ef890df4031 163f510d .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce INFO: task hung in tun_chr_close
2025/03/03 11:00 net-next f77f12010f67 c3901742 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce INFO: task hung in tun_chr_close
2025/02/27 14:00 net-next 0493f7a54e5b 6a8fcbc4 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce INFO: task hung in tun_chr_close
2025/02/21 10:58 net-next 5d6ba5ab8582 0808a665 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce INFO: task hung in tun_chr_close
2025/02/11 10:18 net-next 907dd32b4a8a 43f51a00 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce INFO: task hung in tun_chr_close
2025/02/09 13:50 net-next acdefab0dcbc ef44b750 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce INFO: task hung in tun_chr_close
2025/01/27 11:08 net-next 0ad9617c78ac 9fbd772e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce INFO: task hung in tun_chr_close
2025/06/28 06:57 linux-next 2aeda9592360 fc9d8ee5 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-rust-kasan-gce INFO: task hung in tun_chr_close
2024/10/14 19:39 linux-next 7f773fd61baa 084d8178 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in tun_chr_close
* Struck through repros no longer work on HEAD.