INFO: task hung in tls_push_record

5 views
Skip to first unread message

syzbot

unread,
Nov 4, 2020, 8:33:23 AM11/4/20
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: f5d8eef0 Linux 4.19.154
git tree: linux-4.19.y
console output: https://syzkaller.appspot.com/x/log.txt?x=161d7f14500000
kernel config: https://syzkaller.appspot.com/x/.config?x=be9b9357b4680aa1
dashboard link: https://syzkaller.appspot.com/bug?extid=6e033fbeb30d3ff4860d
compiler: gcc (GCC) 10.1.0-syz 20200507

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

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

audit: type=1804 audit(1604496585.461:66): pid=10553 uid=0 auid=0 ses=4 subj==unconfined op=invalid_pcr cause=open_writers comm="syz-executor.2" name="/root/syzkaller-testdir461883185/syzkaller.WwcGmP/2052/bus" dev="sda1" ino=17007 res=1
audit: type=1804 audit(1604496585.481:67): pid=10575 uid=0 auid=0 ses=4 subj==unconfined op=invalid_pcr cause=ToMToU comm="syz-executor.2" name="/root/syzkaller-testdir461883185/syzkaller.WwcGmP/2052/bus" dev="sda1" ino=17007 res=1
INFO: task syz-executor.2:10557 blocked for more than 140 seconds.
Not tainted 4.19.154-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
syz-executor.2 D27112 10557 13537 0x00000004
Call Trace:
context_switch kernel/sched/core.c:2828 [inline]
__schedule+0x887/0x2040 kernel/sched/core.c:3517
schedule+0x8d/0x1b0 kernel/sched/core.c:3561
schedule_timeout+0x92d/0xfe0 kernel/time/timer.c:1801
do_wait_for_common kernel/sched/completion.c:83 [inline]
__wait_for_common kernel/sched/completion.c:104 [inline]
wait_for_common+0x29c/0x470 kernel/sched/completion.c:115
crypto_wait_req include/linux/crypto.h:517 [inline]
tls_do_encryption net/tls/tls_sw.c:193 [inline]
tls_push_record+0xec4/0x1370 net/tls/tls_sw.c:228
tls_sw_sendpage+0x8c6/0xd00 net/tls/tls_sw.c:585
inet_sendpage+0x164/0x650 net/ipv4/af_inet.c:815
kernel_sendpage net/socket.c:3378 [inline]
sock_sendpage+0xdf/0x140 net/socket.c:847
pipe_to_sendpage+0x268/0x330 fs/splice.c:452
splice_from_pipe_feed fs/splice.c:503 [inline]
__splice_from_pipe+0x389/0x800 fs/splice.c:627
splice_from_pipe fs/splice.c:662 [inline]
generic_splice_sendpage+0xd4/0x140 fs/splice.c:833
do_splice_from fs/splice.c:852 [inline]
direct_splice_actor+0x115/0x160 fs/splice.c:1025
splice_direct_to_actor+0x33f/0x8d0 fs/splice.c:980
do_splice_direct+0x1a7/0x270 fs/splice.c:1068
do_sendfile+0x550/0xc30 fs/read_write.c:1447
__do_sys_sendfile64 fs/read_write.c:1508 [inline]
__se_sys_sendfile64+0x147/0x160 fs/read_write.c:1494
do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x45deb9
Code: Bad RIP value.
RSP: 002b:00007f4a9e874c78 EFLAGS: 00000246 ORIG_RAX: 0000000000000028
RAX: ffffffffffffffda RBX: 0000000000027f40 RCX: 000000000045deb9
RDX: 0000000000000000 RSI: 0000000000000007 RDI: 0000000000000009
RBP: 000000000118c010 R08: 0000000000000000 R09: 0000000000000000
R10: 0000800100020001 R11: 0000000000000246 R12: 000000000118bfd4
R13: 00007ffc77f5eb0f R14: 00007f4a9e8759c0 R15: 000000000118bfd4

Showing all locks held in the system:
1 lock held by khungtaskd/1566:
#0: 00000000bcd63dac (rcu_read_lock){....}, at: debug_show_all_locks+0x53/0x265 kernel/locking/lockdep.c:4440
1 lock held by in:imklog/7799:
#0: 000000009db66866 (&f->f_pos_lock){+.+.}, at: __fdget_pos+0x26f/0x310 fs/file.c:767
1 lock held by syz-executor.2/10557:
#0: 00000000872a0cdd (sk_lock-AF_INET6){+.+.}, at: lock_sock include/net/sock.h:1510 [inline]
#0: 00000000872a0cdd (sk_lock-AF_INET6){+.+.}, at: tls_sw_sendpage+0x151/0xd00 net/tls/tls_sw.c:525

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

NMI backtrace for cpu 1
CPU: 1 PID: 1566 Comm: khungtaskd Not tainted 4.19.154-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
__dump_stack lib/dump_stack.c:77 [inline]
dump_stack+0x1fc/0x2fe lib/dump_stack.c:118
nmi_cpu_backtrace.cold+0x63/0xa2 lib/nmi_backtrace.c:101
nmi_trigger_cpumask_backtrace+0x1a6/0x1eb lib/nmi_backtrace.c:62
trigger_all_cpu_backtrace include/linux/nmi.h:146 [inline]
check_hung_uninterruptible_tasks kernel/hung_task.c:203 [inline]
watchdog+0x991/0xe60 kernel/hung_task.c:287
kthread+0x33f/0x460 kernel/kthread.c:259
ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:415
Sending NMI from CPU 1 to CPUs 0:
NMI backtrace for cpu 0
CPU: 0 PID: 9985 Comm: kworker/u4:7 Not tainted 4.19.154-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Workqueue: bat_events batadv_nc_worker
RIP: 0010:__lock_release kernel/locking/lockdep.c:3685 [inline]
RIP: 0010:lock_release+0x2b6/0x8b0 kernel/locking/lockdep.c:3926
Code: 48 ba 00 00 00 00 00 fc ff df 48 89 f9 48 c1 e9 03 0f b6 0c 11 48 89 fa 83 e2 07 83 c2 01 38 ca 7c 08 84 c9 0f 85 41 05 00 00 <66> f7 40 22 f0 ff 74 37 48 8d 78 20 48 ba 00 00 00 00 00 fc ff df
RSP: 0018:ffff88805acbfc00 EFLAGS: 00000046
RAX: ffff88805cbe48d8 RBX: ffffffff8d23a720 RCX: 0000000000000000
RDX: 0000000000000003 RSI: ffffffff89f85aa0 RDI: ffff88805cbe48fa
RBP: ffffffff89f85aa0 R08: 0000000000000000 R09: 0000000000000001
R10: 0000000000000000 R11: 0000000000000000 R12: 1ffff1100b597f83
R13: ffffffff87f96e55 R14: ffff88805cbe4000 R15: 0000000000000003
FS: 0000000000000000(0000) GS:ffff8880ba000000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f869ee4a000 CR3: 00000000b0a61000 CR4: 00000000001406f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
rcu_lock_release include/linux/rcupdate.h:247 [inline]
rcu_read_unlock include/linux/rcupdate.h:681 [inline]
batadv_nc_purge_orig_hash net/batman-adv/network-coding.c:423 [inline]
batadv_nc_worker+0x66c/0xd50 net/batman-adv/network-coding.c:730
process_one_work+0x864/0x1570 kernel/workqueue.c:2155
worker_thread+0x64c/0x1130 kernel/workqueue.c:2298
kthread+0x33f/0x460 kernel/kthread.c:259
ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:415


---
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.

syzbot

unread,
Mar 4, 2021, 8:33:11 AM3/4/21
to syzkaller...@googlegroups.com
Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.
Reply all
Reply to author
Forward
0 new messages