syzbot


INFO: task hung in tls_sw_cancel_work_tx

Status: auto-obsoleted due to no activity on 2024/02/02 07:08
Reported-by: syzbot+a2bec889efc75058ac70@syzkaller.appspotmail.com
First crash: 393d, last: 393d
Similar bugs (2)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream INFO: task hung in tls_sw_cancel_work_tx net C done error 74 267d 1748d 0/28 closed as dup on 2020/12/29 19:08
linux-6.1 INFO: task hung in tls_sw_cancel_work_tx 3 373d 396d 0/3 auto-obsoleted due to no activity on 2024/02/22 04:34

Sample crash report:
INFO: task syz-executor.5:23538 blocked for more than 143 seconds.
      Not tainted 5.15.136-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.5  state:D stack:    0 pid:23538 ppid:  4015 flags:0x0000000d
Call trace:
 __switch_to+0x308/0x5e8 arch/arm64/kernel/process.c:518
 context_switch kernel/sched/core.c:5026 [inline]
 __schedule+0xf10/0x1e48 kernel/sched/core.c:6372
 schedule+0x11c/0x1c8 kernel/sched/core.c:6455
 schedule_timeout+0xb8/0x344 kernel/time/timer.c:1860
 do_wait_for_common+0x214/0x388 kernel/sched/completion.c:85
 __wait_for_common kernel/sched/completion.c:106 [inline]
 wait_for_common kernel/sched/completion.c:117 [inline]
 wait_for_completion+0x4c/0x64 kernel/sched/completion.c:138
 __flush_work+0x12c/0x1c0 kernel/workqueue.c:3094
 __cancel_work_timer+0x3ec/0x548 kernel/workqueue.c:3181
 cancel_delayed_work_sync+0x24/0x38 kernel/workqueue.c:3313
 tls_sw_cancel_work_tx+0x88/0xf0 net/tls/tls_sw.c:2173
 tls_sk_proto_close+0xf8/0xbc4 net/tls/tls_main.c:308
 inet_release+0x160/0x1d0 net/ipv4/af_inet.c:431
 inet6_release+0x5c/0x78 net/ipv6/af_inet6.c:486
 __sock_release net/socket.c:649 [inline]
 sock_close+0xb8/0x1fc net/socket.c:1334
 __fput+0x30c/0x7f0 fs/file_table.c:280
 ____fput+0x20/0x30 fs/file_table.c:308
 task_work_run+0x130/0x1e4 kernel/task_work.c:164
 get_signal+0x1450/0x1550 kernel/signal.c:2661
 do_signal arch/arm64/kernel/signal.c:890 [inline]
 do_notify_resume+0x3d0/0x32b8 arch/arm64/kernel/signal.c:943
 prepare_exit_to_user_mode arch/arm64/kernel/entry-common.c:133 [inline]
 exit_to_user_mode arch/arm64/kernel/entry-common.c:138 [inline]
 el0_svc+0xfc/0x1f0 arch/arm64/kernel/entry-common.c:609
 el0t_64_sync_handler+0x84/0xe4 arch/arm64/kernel/entry-common.c:626
 el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584
INFO: task syz-executor.4:23540 blocked for more than 143 seconds.
      Not tainted 5.15.136-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.4  state:D stack:    0 pid:23540 ppid:  4009 flags:0x00000005
Call trace:
 __switch_to+0x308/0x5e8 arch/arm64/kernel/process.c:518
 context_switch kernel/sched/core.c:5026 [inline]
 __schedule+0xf10/0x1e48 kernel/sched/core.c:6372
 schedule+0x11c/0x1c8 kernel/sched/core.c:6455
 schedule_timeout+0xb8/0x344 kernel/time/timer.c:1860
 do_wait_for_common+0x214/0x388 kernel/sched/completion.c:85
 __wait_for_common kernel/sched/completion.c:106 [inline]
 wait_for_common kernel/sched/completion.c:117 [inline]
 wait_for_completion+0x4c/0x64 kernel/sched/completion.c:138
 __flush_work+0x12c/0x1c0 kernel/workqueue.c:3094
 __cancel_work_timer+0x3ec/0x548 kernel/workqueue.c:3181
 cancel_delayed_work_sync+0x24/0x38 kernel/workqueue.c:3313
 tls_sw_cancel_work_tx+0x88/0xf0 net/tls/tls_sw.c:2173
 tls_sk_proto_close+0xf8/0xbc4 net/tls/tls_main.c:308
 inet_release+0x160/0x1d0 net/ipv4/af_inet.c:431
 inet6_release+0x5c/0x78 net/ipv6/af_inet6.c:486
 __sock_release net/socket.c:649 [inline]
 sock_close+0xb8/0x1fc net/socket.c:1334
 __fput+0x30c/0x7f0 fs/file_table.c:280
 ____fput+0x20/0x30 fs/file_table.c:308
 task_work_run+0x130/0x1e4 kernel/task_work.c:164
 tracehook_notify_resume include/linux/tracehook.h:189 [inline]
 do_notify_resume+0x262c/0x32b8 arch/arm64/kernel/signal.c:946
 prepare_exit_to_user_mode arch/arm64/kernel/entry-common.c:133 [inline]
 exit_to_user_mode arch/arm64/kernel/entry-common.c:138 [inline]
 el0_svc+0xfc/0x1f0 arch/arm64/kernel/entry-common.c:609
 el0t_64_sync_handler+0x84/0xe4 arch/arm64/kernel/entry-common.c:626
 el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584

Showing all locks held in the system:
1 lock held by khungtaskd/27:
 #0: ffff800014ae1560 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0xc/0x44 include/linux/rcupdate.h:268
2 locks held by getty/3727:
 #0: ffff0000d2e8e098 (&tty->ldisc_sem){++++}-{0:0}, at: ldsem_down_read+0x40/0x50 drivers/tty/tty_ldsem.c:340
 #1: ffff80001a2be2e8 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x414/0x1204 drivers/tty/n_tty.c:2158
2 locks held by syz-executor.3/4010:
3 locks held by kworker/0:4/4067:
 #0: ffff0000c0020d38 ((wq_completion)events){+.+.}-{0:0}, at: process_one_work+0x66c/0x11b8 kernel/workqueue.c:2283
 #1: ffff80001d087c00 ((work_completion)(&(&sw_ctx_tx->tx_work.work)->work)){+.+.}-{0:0}, at: process_one_work+0x6ac/0x11b8 kernel/workqueue.c:2285
 #2: ffff00011f0c54d8 (&ctx->tx_lock){+.+.}-{3:3}, at: tx_work_handler+0xf8/0x240 net/tls/tls_sw.c:2292
3 locks held by kworker/1:5/4070:
 #0: ffff0000c0020d38 ((wq_completion)events){+.+.}-{0:0}, at: process_one_work+0x66c/0x11b8 kernel/workqueue.c:2283
 #1: ffff80001d0b7c00 ((work_completion)(&(&sw_ctx_tx->tx_work.work)->work)){+.+.}-{0:0}, at: process_one_work+0x6ac/0x11b8 kernel/workqueue.c:2285
 #2: ffff0000d19bdcd8 (&ctx->tx_lock){+.+.}-{3:3}, at: tx_work_handler+0xf8/0x240 net/tls/tls_sw.c:2292
1 lock held by syz-executor.5/23538:
 #0: ffff0000df338210 (&sb->s_type->i_mutex_key#11){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:787 [inline]
 #0: ffff0000df338210 (&sb->s_type->i_mutex_key#11){+.+.}-{3:3}, at: __sock_release net/socket.c:648 [inline]
 #0: ffff0000df338210 (&sb->s_type->i_mutex_key#11){+.+.}-{3:3}, at: sock_close+0x80/0x1fc net/socket.c:1334
1 lock held by syz-executor.4/23540:
 #0: ffff0000df0aca10 (&sb->s_type->i_mutex_key#11){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:787 [inline]
 #0: ffff0000df0aca10 (&sb->s_type->i_mutex_key#11){+.+.}-{3:3}, at: __sock_release net/socket.c:648 [inline]
 #0: ffff0000df0aca10 (&sb->s_type->i_mutex_key#11){+.+.}-{3:3}, at: sock_close+0x80/0x1fc net/socket.c:1334
1 lock held by syz-executor.3/27010:
1 lock held by syz-executor.5/27011:
 #0: ffff0001b4807d18 (&rq->__lock){-.-.}-{2:2}, at: raw_spin_rq_lock_nested kernel/sched/core.c:475 [inline]
 #0: ffff0001b4807d18 (&rq->__lock){-.-.}-{2:2}, at: raw_spin_rq_lock kernel/sched/sched.h:1326 [inline]
 #0: ffff0001b4807d18 (&rq->__lock){-.-.}-{2:2}, at: rq_lock kernel/sched/sched.h:1621 [inline]
 #0: ffff0001b4807d18 (&rq->__lock){-.-.}-{2:2}, at: __schedule+0x328/0x1e48 kernel/sched/core.c:6286
5 locks held by syz-executor.5/27012:

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


Crashes (1):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2023/10/25 07:08 linux-5.15.y 00c03985402e 17e6d526 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 INFO: task hung in tls_sw_cancel_work_tx
* Struck through repros no longer work on HEAD.