[v6.1] INFO: task hung in tls_sw_cancel_work_tx

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 7d24402875c7 Linux 6.1.59
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=127c7d15680000
kernel config: https://syzkaller.appspot.com/x/.config?x=f4e0bf6ab3a898ce
dashboard link: https://syzkaller.appspot.com/bug?extid=16b7b4a88091943a02b2
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm64

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/8d6fe63103c3/disk-7d244028.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/91b66825c240/vmlinux-7d244028.xz
kernel image: https://storage.googleapis.com/syzbot-assets/2c90616935ea/Image-7d244028.gz.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+16b7b4...@syzkaller.appspotmail.com

INFO: task syz-executor.1:6169 blocked for more than 143 seconds.
Not tainted 6.1.59-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.1 state:D stack:0 pid:6169 ppid:4269 flags:0x00000005
Call trace:
__switch_to+0x320/0x754 arch/arm64/kernel/process.c:553
context_switch kernel/sched/core.c:5241 [inline]
__schedule+0xee4/0x1c98 kernel/sched/core.c:6554
schedule+0xc4/0x170 kernel/sched/core.c:6630
schedule_timeout+0xb8/0x344 kernel/time/timer.c:1911
do_wait_for_common+0x30c/0x468 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+0x48/0x60 kernel/sched/completion.c:138
__flush_work+0x12c/0x1c0 kernel/workqueue.c:3076
__cancel_work_timer+0x3ec/0x548 kernel/workqueue.c:3163
cancel_delayed_work_sync+0x24/0x38 kernel/workqueue.c:3304
tls_sw_cancel_work_tx+0x80/0xd0 net/tls/tls_sw.c:2313
tls_sk_proto_close+0xf8/0xbc4 net/tls/tls_main.c:327
inet_release+0x160/0x1d0 net/ipv4/af_inet.c:429
inet6_release+0x5c/0x78 net/ipv6/af_inet6.c:490
__sock_release net/socket.c:652 [inline]
sock_close+0xb8/0x1fc net/socket.c:1387
__fput+0x30c/0x7bc fs/file_table.c:320
____fput+0x20/0x30 fs/file_table.c:348
task_work_run+0x240/0x2f0 kernel/task_work.c:179
resume_user_mode_work include/linux/resume_user_mode.h:49 [inline]
do_notify_resume+0x2148/0x3474 arch/arm64/kernel/signal.c:1132
prepare_exit_to_user_mode arch/arm64/kernel/entry-common.c:137 [inline]
exit_to_user_mode arch/arm64/kernel/entry-common.c:142 [inline]
el0_svc+0x9c/0x168 arch/arm64/kernel/entry-common.c:638
el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655
el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:585

Showing all locks held in the system:
1 lock held by rcu_tasks_kthre/12:
#0: ffff800015a84d70 (rcu_tasks.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x44/0xcf4 kernel/rcu/tasks.h:516
1 lock held by rcu_tasks_trace/13:
#0: ffff800015a85570 (rcu_tasks_trace.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x44/0xcf4 kernel/rcu/tasks.h:516
1 lock held by khungtaskd/28:
#0: ffff800015a84ba0 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0xc/0x44 include/linux/rcupdate.h:305
4 locks held by kworker/u4:5/1738:
2 locks held by getty/3980:
#0: ffff0000d5fd5098 (&tty->ldisc_sem){++++}-{0:0}, at: ldsem_down_read+0x3c/0x4c drivers/tty/tty_ldsem.c:340
#1: ffff80001bd602f0 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x414/0x1214 drivers/tty/n_tty.c:2188
1 lock held by syz-executor.2/4281:
3 locks held by kworker/1:10/6003:
#0: ffff0000c0020d38 ((wq_completion)events){+.+.}-{0:0}, at: process_one_work+0x664/0x1404 kernel/workqueue.c:2265
#1: ffff800021b57c20 ((work_completion)(&(&sw_ctx_tx->tx_work.work)->work)){+.+.}-{0:0}, at: process_one_work+0x6a8/0x1404 kernel/workqueue.c:2267
#2: ffff000121cb40d8 (&ctx->tx_lock){+.+.}-{3:3}, at: tx_work_handler+0xf4/0x220 net/tls/tls_sw.c:2430
1 lock held by syz-executor.1/6169:
#0: ffff000125e79410 (&sb->s_type->i_mutex_key#11){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:756 [inline]
#0: ffff000125e79410 (&sb->s_type->i_mutex_key#11){+.+.}-{3:3}, at: __sock_release net/socket.c:651 [inline]
#0: ffff000125e79410 (&sb->s_type->i_mutex_key#11){+.+.}-{3:3}, at: sock_close+0x80/0x1fc net/socket.c:1387
1 lock held by syz-executor.4/8429:
#0: ffff000151555010 (&sb->s_type->i_mutex_key#11){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:756 [inline]
#0: ffff000151555010 (&sb->s_type->i_mutex_key#11){+.+.}-{3:3}, at: __sock_release net/socket.c:651 [inline]
#0: ffff000151555010 (&sb->s_type->i_mutex_key#11){+.+.}-{3:3}, at: sock_close+0x80/0x1fc net/socket.c:1387
5 locks held by syz-executor.3/8444:
2 locks held by syz-executor.0/8446:

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



---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzk...@googlegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

If the bug is already fixed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want to overwrite bug's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the bug is a duplicate of another bug, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 00c03985402e Linux 5.15.136
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=13cff895680000
kernel config: https://syzkaller.appspot.com/x/.config?x=44f1119854f35733
dashboard link: https://syzkaller.appspot.com/bug?extid=a2bec889efc75058ac70

compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm64

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:

disk image: https://storage.googleapis.com/syzbot-assets/8b6792bef09d/disk-00c03985.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/d63de1cd585e/vmlinux-00c03985.xz
kernel image: https://storage.googleapis.com/syzbot-assets/90e251933a79/Image-00c03985.gz.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:

Reported-by: syzbot+a2bec8...@syzkaller.appspotmail.com

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:

[syzbot]

Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.

[syzbot]