syzbot


INFO: task hung in tls_sk_proto_close

Status: upstream: reported C repro on 2020/03/30 07:09
Reported-by: syzbot+ca1345cca66556f3d79b@syzkaller.appspotmail.com
First crash: 844d, last: 2d20h

Cause bisection: introduced by (bisect log) :
commit 02d21b59d5cc4b4b395bbc2a29319b8a529ebeff
Author: Ido Schimmel <idosch@mellanox.com>
Date: Wed Jan 23 14:32:59 2019 +0000

  mlxsw: spectrum_nve: Enable VXLAN on Spectrum-2

Crash: general protection fault in batadv_iv_ogm_queue_add (log)
Repro: C syz .config
duplicates (1):
Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
INFO: task hung in tls_sw_cancel_work_tx C done error 58 786d 873d 0/22 closed as dup on 2020/12/29 19:08
similar bugs (2):
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream INFO: task can't die in p9_fd_close C done 58 66d 672d 0/22 upstream: reported C repro on 2020/08/26 10:38
upstream INFO: task can't die in tls_sk_proto_close 2 670d 679d 0/22 auto-closed as invalid on 2020/10/27 23:55

Sample crash report:
INFO: task syz-executor192:3645 blocked for more than 143 seconds.
      Not tainted 5.18.0-rc4-syzkaller-00064-g8f4dd16603ce #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor192 state:D stack:23680 pid: 3645 ppid:  3625 flags:0x00000004
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5073 [inline]
 __schedule+0xa9a/0x4cc0 kernel/sched/core.c:6388
 schedule+0xd2/0x1f0 kernel/sched/core.c:6460
 schedule_timeout+0x1db/0x2a0 kernel/time/timer.c:1860
 do_wait_for_common kernel/sched/completion.c:85 [inline]
 __wait_for_common+0x373/0x530 kernel/sched/completion.c:106
 __flush_work+0x56c/0xb10 kernel/workqueue.c:3075
 __cancel_work_timer+0x3f9/0x570 kernel/workqueue.c:3162
 tls_sk_proto_close+0x4a7/0xaf0 net/tls/tls_main.c:307
 inet_release+0x12e/0x280 net/ipv4/af_inet.c:428
 inet6_release+0x4c/0x70 net/ipv6/af_inet6.c:481
 __sock_release+0xcd/0x280 net/socket.c:650
 sock_close+0x18/0x20 net/socket.c:1318
 __fput+0x277/0x9d0 fs/file_table.c:317
 task_work_run+0xdd/0x1a0 kernel/task_work.c:164
 resume_user_mode_work include/linux/resume_user_mode.h:49 [inline]
 exit_to_user_mode_loop kernel/entry/common.c:169 [inline]
 exit_to_user_mode_prepare+0x23c/0x250 kernel/entry/common.c:201
 __syscall_exit_to_user_mode_work kernel/entry/common.c:283 [inline]
 syscall_exit_to_user_mode+0x19/0x60 kernel/entry/common.c:294
 do_syscall_64+0x42/0xb0 arch/x86/entry/common.c:86
 entry_SYSCALL_64_after_hwframe+0x44/0xae
RIP: 0033:0x7f26b364e753
RSP: 002b:00007ffed5ac85b8 EFLAGS: 00000246 ORIG_RAX: 0000000000000003
RAX: 0000000000000000 RBX: 0000000000000006 RCX: 00007f26b364e753
RDX: fffffffffffffe60 RSI: 00000000200005c0 RDI: 0000000000000005
RBP: 0000000000000000 R08: 0000000000000000 R09: fffffffffffffe60
R10: 0000000000000000 R11: 0000000000000246 R12: 00007ffed5ac85d0
R13: 00000000000f4240 R14: 0000000000000000 R15: 0000000000000000
 </TASK>

Showing all locks held in the system:
3 locks held by kworker/0:1/14:
 #0: ffff888010c67d38 ((wq_completion)events){+.+.}-{0:0}, at: arch_atomic64_set arch/x86/include/asm/atomic64_64.h:34 [inline]
 #0: ffff888010c67d38 ((wq_completion)events){+.+.}-{0:0}, at: arch_atomic_long_set include/linux/atomic/atomic-long.h:41 [inline]
 #0: ffff888010c67d38 ((wq_completion)events){+.+.}-{0:0}, at: atomic_long_set include/linux/atomic/atomic-instrumented.h:1280 [inline]
 #0: ffff888010c67d38 ((wq_completion)events){+.+.}-{0:0}, at: set_work_data kernel/workqueue.c:636 [inline]
 #0: ffff888010c67d38 ((wq_completion)events){+.+.}-{0:0}, at: set_work_pool_and_clear_pending kernel/workqueue.c:663 [inline]
 #0: ffff888010c67d38 ((wq_completion)events){+.+.}-{0:0}, at: process_one_work+0x87a/0x1610 kernel/workqueue.c:2260
 #1: ffffc9000034fda8 ((work_completion)(&(&sw_ctx_tx->tx_work.work)->work)){+.+.}-{0:0}, at: process_one_work+0x8ae/0x1610 kernel/workqueue.c:2264
 #2: ffff8880787afcd8 (&ctx->tx_lock){+.+.}-{3:3}, at: tx_work_handler+0x127/0x190 net/tls/tls_sw.c:2300
1 lock held by khungtaskd/28:
 #0: ffffffff8bd7f5e0 (rcu_read_lock){....}-{1:2}, at: debug_show_all_locks+0x53/0x260 kernel/locking/lockdep.c:6467
3 locks held by kworker/1:2/141:
2 locks held by getty/3274:
 #0: ffff88814c431098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x22/0x80 drivers/tty/tty_ldisc.c:244
 #1: ffffc90001bf92e8 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0xcea/0x1230 drivers/tty/n_tty.c:2075
1 lock held by syz-executor192/3645:
 #0: ffff8880712d5510 (&sb->s_type->i_mutex_key#10){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:748 [inline]
 #0: ffff8880712d5510 (&sb->s_type->i_mutex_key#10){+.+.}-{3:3}, at: __sock_release+0x86/0x280 net/socket.c:649

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

NMI backtrace for cpu 0
CPU: 0 PID: 28 Comm: khungtaskd Not tainted 5.18.0-rc4-syzkaller-00064-g8f4dd16603ce #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0xcd/0x134 lib/dump_stack.c:106
 nmi_cpu_backtrace.cold+0x47/0x144 lib/nmi_backtrace.c:111
 nmi_trigger_cpumask_backtrace+0x1e6/0x230 lib/nmi_backtrace.c:62
 trigger_all_cpu_backtrace include/linux/nmi.h:146 [inline]
 check_hung_uninterruptible_tasks kernel/hung_task.c:212 [inline]
 watchdog+0xc1d/0xf50 kernel/hung_task.c:369
 kthread+0x2e9/0x3a0 kernel/kthread.c:376
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:298
 </TASK>
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1
CPU: 1 PID: 60 Comm: kworker/u4:3 Not tainted 5.18.0-rc4-syzkaller-00064-g8f4dd16603ce #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Workqueue: events_unbound toggle_allocation_gate
RIP: 0010:debug_smp_processor_id+0x13/0x20 lib/smp_processor_id.c:60
Code: 28 48 c7 c7 60 a3 26 8a e8 6a e8 bb ff e8 e2 28 cc ff eb a2 0f 1f 00 0f 1f 44 00 00 48 c7 c6 a0 a3 26 8a 48 c7 c7 e0 a3 26 8a <e9> 78 fe ff ff 0f 1f 84 00 00 00 00 00 55 48 89 fd 0f 1f 44 00 00
RSP: 0018:ffffc90001c0f938 EFLAGS: 00000086
RAX: 0000000000000001 RBX: 0000000000000001 RCX: ffffffff8135c5f1
RDX: dffffc0000000000 RSI: ffffffff8a26a3a0 RDI: ffffffff8a26a3e0
RBP: ffff8881401a4040 R08: 0000000000000000 R09: ffffffff8db81e17
R10: fffffbfff1b703c2 R11: 000000000000003f R12: 0000000000000001
R13: 0000000000000000 R14: 0000000000000000 R15: 000000000001744c
FS:  0000000000000000(0000) GS:ffff8880b9d00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00005631ac21ca88 CR3: 0000000011e2a000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 rcu_dynticks_curr_cpu_in_eqs kernel/rcu/tree.c:341 [inline]
 rcu_is_watching+0xe/0xb0 kernel/rcu/tree.c:1138
 rcu_read_lock_held_common kernel/rcu/update.c:108 [inline]
 rcu_read_lock_sched_held+0x1c/0x70 kernel/rcu/update.c:123
 trace_tlb_flush include/trace/events/tlb.h:38 [inline]
 trace_tlb_flush+0x126/0x1b0 include/trace/events/tlb.h:38
 switch_mm_irqs_off+0x4a4/0xa10 arch/x86/mm/tlb.c:630
 use_temporary_mm arch/x86/kernel/alternative.c:962 [inline]
 __text_poke+0x44a/0x8c0 arch/x86/kernel/alternative.c:1059
 text_poke arch/x86/kernel/alternative.c:1121 [inline]
 text_poke_bp_batch+0x375/0x6b0 arch/x86/kernel/alternative.c:1385
 text_poke_flush arch/x86/kernel/alternative.c:1542 [inline]
 text_poke_flush arch/x86/kernel/alternative.c:1539 [inline]
 text_poke_finish+0x16/0x30 arch/x86/kernel/alternative.c:1549
 arch_jump_label_transform_apply+0x13/0x20 arch/x86/kernel/jump_label.c:146
 jump_label_update+0x32f/0x410 kernel/jump_label.c:830
 static_key_enable_cpuslocked+0x1b1/0x260 kernel/jump_label.c:177
 static_key_enable+0x16/0x20 kernel/jump_label.c:190
 toggle_allocation_gate mm/kfence/core.c:764 [inline]
 toggle_allocation_gate+0x100/0x390 mm/kfence/core.c:756
 process_one_work+0x996/0x1610 kernel/workqueue.c:2289
 worker_thread+0x665/0x1080 kernel/workqueue.c:2436
 kthread+0x2e9/0x3a0 kernel/kthread.c:376
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:298
 </TASK>
INFO: NMI handler (nmi_cpu_backtrace_handler) took too long to run: 1.181 msecs
----------------
Code disassembly (best guess), 1 bytes skipped:
   0:	48 c7 c7 60 a3 26 8a 	mov    $0xffffffff8a26a360,%rdi
   7:	e8 6a e8 bb ff       	callq  0xffbbe876
   c:	e8 e2 28 cc ff       	callq  0xffcc28f3
  11:	eb a2                	jmp    0xffffffb5
  13:	0f 1f 00             	nopl   (%rax)
  16:	0f 1f 44 00 00       	nopl   0x0(%rax,%rax,1)
  1b:	48 c7 c6 a0 a3 26 8a 	mov    $0xffffffff8a26a3a0,%rsi
  22:	48 c7 c7 e0 a3 26 8a 	mov    $0xffffffff8a26a3e0,%rdi
* 29:	e9 78 fe ff ff       	jmpq   0xfffffea6 <-- trapping instruction
  2e:	0f 1f 84 00 00 00 00 	nopl   0x0(%rax,%rax,1)
  35:	00
  36:	55                   	push   %rbp
  37:	48 89 fd             	mov    %rdi,%rbp
  3a:	0f 1f 44 00 00       	nopl   0x0(%rax,%rax,1)

Crashes (697):
Manager Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Title
ci-upstream-kasan-gce-selinux-root 2022/04/28 15:17 upstream 8f4dd16603ce 8a1f1f07 .config log report syz C INFO: task hung in tls_sk_proto_close
ci-upstream-kasan-gce-smack-root 2022/04/21 12:15 upstream b253435746d9 d4befee1 .config log report syz C INFO: task hung in tls_sk_proto_close
ci-upstream-kasan-gce-smack-root 2022/03/23 18:43 upstream 6b1f86f8e9c7 5ff41e94 .config log report syz C INFO: task hung in tls_sk_proto_close
ci-upstream-kasan-gce-root 2022/03/01 13:57 upstream 719fce7539cd 45a13a73 .config log report syz C INFO: task hung in tls_sk_proto_close
ci-upstream-kasan-gce-selinux-root 2021/02/18 12:03 upstream f40ddce88593 14052202 .config log report syz C INFO: task hung in tls_sk_proto_close
ci-upstream-net-this-kasan-gce 2022/04/22 01:26 net bc6de2878429 2738b391 .config log report syz C INFO: task hung in tls_sk_proto_close
ci-upstream-net-this-kasan-gce 2021/08/08 00:29 net 34737e1320db 6972b106 .config log report syz C INFO: task hung in tls_sk_proto_close
ci-upstream-net-kasan-gce 2022/04/22 07:51 net-next 9c8774e629a1 2738b391 .config log report syz C INFO: task hung in tls_sk_proto_close
ci-upstream-net-kasan-gce 2021/08/08 00:26 net-next f9be84db09d2 6972b106 .config log report syz C INFO: task hung in tls_sk_proto_close
ci-upstream-kasan-gce-selinux-root 2020/09/10 14:25 upstream 34d4ddd359db 409809d8 .config log report syz C
ci-upstream-kasan-gce-root 2020/09/09 15:22 upstream 34d4ddd359db 0ea7a887 .config log report syz C
ci-upstream-kasan-gce 2020/09/05 16:13 upstream c70672d8d316 abf9ba4f .config log report syz C
ci-upstream-kasan-gce-root 2020/08/30 16:20 upstream 1127b219ce94 d5a3ae1f .config log report syz C
ci-upstream-kasan-gce-selinux-root 2020/08/30 10:22 upstream 1127b219ce94 d5a3ae1f .config log report syz C
ci-upstream-kasan-gce 2020/08/30 10:15 upstream 1127b219ce94 d5a3ae1f .config log report syz C
ci-upstream-kasan-gce-386 2020/09/05 16:14 upstream c70672d8d316 abf9ba4f .config log report syz C
ci-upstream-kasan-gce-386 2020/08/29 23:33 upstream 4d41ead6ead9 d5a3ae1f .config log report syz C
ci-upstream-net-this-kasan-gce 2020/09/05 04:15 net b61ac5bb420a abf9ba4f .config log report syz C
ci-upstream-net-this-kasan-gce 2020/08/29 09:33 net 5438dd45831e d5a3ae1f .config log report syz C
ci-upstream-net-kasan-gce 2020/10/15 15:34 net-next d25e2e9388ed 63869021 .config log report syz C
ci-upstream-net-kasan-gce 2020/09/05 05:15 net-next 3ab1270bfa1e abf9ba4f .config log report syz C
ci-upstream-net-kasan-gce 2020/09/05 00:58 net-next 3ab1270bfa1e abf9ba4f .config log report syz C
ci-upstream-net-kasan-gce 2020/08/29 10:13 net-next 0baf01942d3d d5a3ae1f .config log report syz C
ci-upstream-linux-next-kasan-gce-root 2021/08/07 20:20 linux-next 7999516e20bd 6972b106 .config log report syz C INFO: task can't die in tls_sk_proto_close
ci-upstream-linux-next-kasan-gce-root 2020/09/23 10:44 linux-next e64997027d5f 3e8f6c27 .config log report syz C
ci-upstream-linux-next-kasan-gce-root 2020/08/31 03:55 linux-next b36c969764ab d5a3ae1f .config log report syz C
ci-upstream-linux-next-kasan-gce-root 2020/08/29 06:08 linux-next b36c969764ab d5a3ae1f .config log report syz C
ci-upstream-kasan-gce 2022/06/23 14:02 upstream de5c208d533a 912f5df7 .config log report info INFO: task hung in tls_sk_proto_close
ci-upstream-kasan-gce 2022/06/22 00:53 upstream ca1fdab7fd27 0fc5c330 .config log report info INFO: task hung in tls_sk_proto_close
ci-upstream-kasan-gce 2022/06/19 19:13 upstream 05c6ca8512f2 8f633d84 .config log report info INFO: task hung in tls_sk_proto_close
ci-upstream-kasan-gce-smack-root 2022/06/17 01:40 upstream 48a23ec6ff2b 1719ee24 .config log report info INFO: task hung in tls_sk_proto_close
ci-upstream-kasan-gce 2022/06/16 09:35 upstream 30306f6194ca 1719ee24 .config log report info INFO: task hung in tls_sk_proto_close
ci-upstream-kasan-gce 2022/06/14 18:45 upstream 24625f7d91fb 127d1faf .config log report info INFO: task hung in tls_sk_proto_close
ci-upstream-kasan-gce 2022/06/12 19:14 upstream 7a68065eb9cd 0d5abf15 .config log report info INFO: task hung in tls_sk_proto_close
ci-upstream-kasan-gce 2022/06/12 01:19 upstream 7a68065eb9cd 0d5abf15 .config log report info INFO: task hung in tls_sk_proto_close
ci-upstream-kasan-gce-selinux-root 2022/06/10 23:11 upstream fe43c0188911 0d5abf15 .config log report info INFO: task hung in tls_sk_proto_close
ci-upstream-kasan-gce-smack-root 2022/06/10 16:15 upstream 6bfb56e93bce 0d5abf15 .config log report info INFO: task hung in tls_sk_proto_close
ci-upstream-kasan-gce-selinux-root 2022/06/06 17:37 upstream f2906aa86338 c8857892 .config log report info INFO: task hung in tls_sk_proto_close
ci-upstream-kasan-gce 2022/05/23 08:10 upstream 4b0986a3613c 7268fa62 .config log report info INFO: task hung in tls_sk_proto_close
ci-upstream-kasan-gce 2022/05/17 06:57 upstream 42226c989789 744a39e2 .config log report info INFO: task hung in tls_sk_proto_close
ci-upstream-kasan-gce-smack-root 2022/03/30 07:52 upstream d888c83fcec7 6bdac766 .config log report info INFO: task hung in tls_sk_proto_close
ci-upstream-kasan-gce-root 2022/03/26 22:23 upstream bddac7c1e02b 89bc8608 .config log report info INFO: task hung in tls_sk_proto_close
ci-upstream-kasan-gce 2022/03/26 14:01 upstream 52d543b5497c 89bc8608 .config log report info INFO: task hung in tls_sk_proto_close
ci-upstream-kasan-gce-selinux-root 2022/03/12 08:22 upstream 68453767131a 9e8eaa75 .config log report info INFO: task hung in tls_sk_proto_close
ci-upstream-kasan-gce 2022/03/10 08:01 upstream e7e19defa575 9e8eaa75 .config log report info INFO: task hung in tls_sk_proto_close
ci-upstream-kasan-gce-386 2022/05/24 04:57 upstream 1e57930e9f40 e7f9308d .config log report info INFO: task hung in tls_sk_proto_close
ci-upstream-kasan-gce-386 2022/03/27 00:09 upstream bddac7c1e02b 89bc8608 .config log report info INFO: task hung in tls_sk_proto_close
ci-upstream-kasan-gce-386 2022/03/08 12:04 upstream ea4424be1688 7bdd8b2c .config log report info INFO: task hung in tls_sk_proto_close
ci-upstream-net-this-kasan-gce 2022/06/21 08:07 net 69135c572d1f 0fc5c330 .config log report info INFO: task hung in tls_sk_proto_close
ci-upstream-net-this-kasan-gce 2022/06/18 06:33 net 582573f1b23d 8f633d84 .config log report info INFO: task hung in tls_sk_proto_close
ci-upstream-net-this-kasan-gce 2022/06/17 10:04 net 48a23ec6ff2b 1719ee24 .config log report info INFO: task hung in tls_sk_proto_close
ci-upstream-net-this-kasan-gce 2022/06/14 07:43 net 619c010a6539 0f087040 .config log report info INFO: task hung in tls_sk_proto_close
ci-upstream-net-this-kasan-gce 2022/06/14 02:47 net 619c010a6539 0f087040 .config log report info INFO: task hung in tls_sk_proto_close
ci-upstream-net-this-kasan-gce 2022/06/12 20:32 net 6f0e1efc880a 0d5abf15 .config log report info INFO: task hung in tls_sk_proto_close
ci-upstream-net-this-kasan-gce 2022/06/12 15:24 net 6f0e1efc880a 0d5abf15 .config log report info INFO: task hung in tls_sk_proto_close
ci-upstream-net-this-kasan-gce 2022/06/11 23:34 net 6f0e1efc880a 0d5abf15 .config log report info INFO: task hung in tls_sk_proto_close
ci-upstream-net-this-kasan-gce 2022/06/10 07:33 net 647df0d41b6b 0d5abf15 .config log report info INFO: task hung in tls_sk_proto_close
ci-upstream-net-this-kasan-gce 2022/05/23 12:11 net 8c3b8dc5cc9b 4c7657cb .config log report info INFO: task hung in tls_sk_proto_close
ci-upstream-net-this-kasan-gce 2022/04/30 02:16 net 4f159a7c4d1b 44a5ca63 .config log report info INFO: task hung in tls_sk_proto_close
ci-upstream-net-this-kasan-gce 2022/04/18 18:21 net d94ef51d5b96 8bcc32a6 .config log report info INFO: task hung in tls_sk_proto_close
ci-upstream-net-this-kasan-gce 2022/04/17 01:29 net d08ed852560e 8bcc32a6 .config log report info INFO: task hung in tls_sk_proto_close
ci-upstream-net-this-kasan-gce 2022/04/04 02:51 net 692930cc4350 79a2a8fc .config log report info INFO: task hung in tls_sk_proto_close
ci-upstream-net-this-kasan-gce 2022/04/01 10:46 net 2975dbdc3989 68fc921a .config log report info INFO: task hung in tls_sk_proto_close
ci-upstream-net-this-kasan-gce 2022/03/31 08:36 net c9ad266bbef5 9d49f3a7 .config log report info INFO: task hung in tls_sk_proto_close
ci-upstream-net-this-kasan-gce 2022/03/22 19:22 net 6a7d8cff4a33 d88ef0c5 .config log report info INFO: task hung in tls_sk_proto_close
ci-upstream-net-this-kasan-gce 2022/03/20 14:07 net 0caf6d992219 e2d91b1d .config log report info INFO: task hung in tls_sk_proto_close
ci-upstream-net-this-kasan-gce 2022/03/18 11:25 net 551acdc3c3d2 e2d91b1d .config log report info INFO: task hung in tls_sk_proto_close
ci-upstream-net-this-kasan-gce 2022/03/15 10:50 net 15d703921f06 9e8eaa75 .config log report info INFO: task hung in tls_sk_proto_close
ci-upstream-net-this-kasan-gce 2022/03/14 06:41 net 8e6ed963763f 9e8eaa75 .config log report info INFO: task hung in tls_sk_proto_close
ci-upstream-net-this-kasan-gce 2022/03/12 09:35 net 46b348fd2d81 9e8eaa75 .config log report info INFO: task hung in tls_sk_proto_close
ci-upstream-net-this-kasan-gce 2022/03/11 01:30 net 5f1474760578 9e8eaa75 .config log report info INFO: task hung in tls_sk_proto_close
ci-upstream-net-kasan-gce 2022/06/27 06:37 net-next ebeae54d3a77 a371c43c .config log report info INFO: task hung in tls_sk_proto_close
ci-upstream-net-kasan-gce 2022/06/12 07:59 net-next e10b02ee5b6c 0d5abf15 .config log report info INFO: task hung in tls_sk_proto_close
ci-upstream-net-kasan-gce 2022/06/12 02:51 net-next e10b02ee5b6c 0d5abf15 .config log report info INFO: task hung in tls_sk_proto_close
ci-upstream-net-kasan-gce 2022/06/04 22:04 net-next 58f9d52ff689 c8857892 .config log report info INFO: task hung in tls_sk_proto_close
ci-upstream-net-kasan-gce 2022/06/03 18:57 net-next 58f9d52ff689 eee80d3c .config log report info INFO: task hung in tls_sk_proto_close
ci-upstream-net-kasan-gce 2022/04/15 15:17 net-next edf45f007a31 8bcc32a6 .config log report info INFO: task hung in tls_sk_proto_close
ci-upstream-net-kasan-gce 2022/04/08 02:08 net-next e8bd70250a82 c6ff3e05 .config log report info INFO: task hung in tls_sk_proto_close
ci-upstream-net-kasan-gce 2022/03/31 17:22 net-next d717e4cae0fe c4c32d8c .config log report info INFO: task hung in tls_sk_proto_close
ci-upstream-net-kasan-gce 2022/03/25 14:32 net-next 169e77764adc 89bc8608 .config log report info INFO: task hung in tls_sk_proto_close
ci-upstream-net-kasan-gce 2022/03/24 13:21 net-next 89695196f0ba 89bc8608 .config log report info INFO: task hung in tls_sk_proto_close
ci-upstream-linux-next-kasan-gce-root 2022/05/28 13:51 linux-next d3fde8ff50ab a46af346 .config log report info INFO: task hung in tls_sk_proto_close
ci-upstream-net-kasan-gce 2021/01/16 23:25 net-next 9ab7e76aefc9 65a7a854 .config log report info
ci-upstream-net-kasan-gce 2020/03/29 19:13 net-next 1a147b74c2fd 05736b29 .config log report
ci-upstream-net-kasan-gce 2020/03/07 10:44 net-next 68e2c37690b0 fd2a5f28 .config log report
ci-upstream-linux-next-kasan-gce-root 2022/02/11 20:44 linux-next ef6b35306dd8 8b9ca619 .config log report info INFO: task can't die in tls_sk_proto_close