syzbot


INFO: task hung in pfkey_release

Status: auto-closed as invalid on 2019/09/29 19:32
Subsystems: net
[Documentation on labels]
Reported-by: syzbot+0053c84a756342365f9b@syzkaller.appspotmail.com
First crash: 2177d, last: 1851d

Sample crash report:
INFO: task syz-executor.0:8170 blocked for more than 143 seconds.
      Not tainted 5.1.0-rc3+ #49
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
syz-executor.0  D28552  8170   7813 0x00000004
Call Trace:
 context_switch kernel/sched/core.c:2877 [inline]
 __schedule+0x817/0x1cc0 kernel/sched/core.c:3518
 schedule+0x92/0x180 kernel/sched/core.c:3562
 exp_funnel_lock kernel/rcu/tree_exp.h:308 [inline]
 synchronize_rcu_expedited+0x54e/0x5b0 kernel/rcu/tree_exp.h:758
 synchronize_rcu.part.0+0x76/0xe0 kernel/rcu/tree.c:3043
 synchronize_rcu+0x27/0xa0 kernel/rcu/tree.c:3046
 pfkey_release+0x270/0x340 net/key/af_key.c:193
 __sock_release+0xd3/0x2b0 net/socket.c:599
 sock_close+0x1b/0x30 net/socket.c:1247
 __fput+0x2e5/0x8d0 fs/file_table.c:278
 ____fput+0x16/0x20 fs/file_table.c:309
 task_work_run+0x14a/0x1c0 kernel/task_work.c:113
 tracehook_notify_resume include/linux/tracehook.h:188 [inline]
 exit_to_usermode_loop+0x273/0x2c0 arch/x86/entry/common.c:166
 prepare_exit_to_usermode arch/x86/entry/common.c:197 [inline]
 syscall_return_slowpath arch/x86/entry/common.c:268 [inline]
 do_syscall_64+0x52d/0x610 arch/x86/entry/common.c:293
 entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x4582b9
Code: 42 08 48 89 04 24 e8 c6 ee fc ff 48 8b 6c 24 08 48 83 c4 10 c3 e8 07 1c 00 00 eb c5 cc cc cc cc cc 64 48 8b 0c 25 f8 ff ff ff <48> 3b 61 10 0f 86 9b 00 00 00 48 83 ec 28 48 89 6c 24 20 48 8d 6c
RSP: 002b:00007f87a12c5c78 EFLAGS: 00000246 ORIG_RAX: 0000000000000021
RAX: 0000000000000009 RBX: 0000000000000002 RCX: 00000000004582b9
RDX: 0000000000000000 RSI: 0000000000000009 RDI: 000000000000000a
RBP: 000000000073bf00 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00007f87a12c66d4
R13: 00000000004be777 R14: 00000000004cf3f0 R15: 00000000ffffffff

Showing all locks held in the system:
1 lock held by khungtaskd/1042:
 #0: 00000000530df645 (rcu_read_lock){....}, at: debug_show_all_locks+0x5f/0x27e kernel/locking/lockdep.c:5061
3 locks held by kworker/u4:4/2627:
 #0: 00000000474799ee (&rq->lock){-.-.}, at: rq_lock kernel/sched/sched.h:1168 [inline]
 #0: 00000000474799ee (&rq->lock){-.-.}, at: __schedule+0x1fc/0x1cc0 kernel/sched/core.c:3456
 #1: 00000000530df645 (rcu_read_lock){....}, at: __update_idle_core+0x45/0x3f0 kernel/sched/fair.c:6059
 #2: 0000000069f5c886 (&base->lock){..-.}, at: lock_timer_base+0x56/0x1b0 kernel/time/timer.c:937
1 lock held by rsyslogd/7687:
 #0: 0000000051766550 (&f->f_pos_lock){+.+.}, at: __fdget_pos+0xee/0x110 fs/file.c:801
2 locks held by getty/7778:
 #0: 00000000562a8044 (&tty->ldisc_sem){++++}, at: ldsem_down_read+0x33/0x40 drivers/tty/tty_ldsem.c:341
 #1: 00000000726ebb9a (&ldata->atomic_read_lock){+.+.}, at: n_tty_read+0x232/0x1b70 drivers/tty/n_tty.c:2156
2 locks held by getty/7779:
 #0: 00000000dd277401 (&tty->ldisc_sem){++++}, at: ldsem_down_read+0x33/0x40 drivers/tty/tty_ldsem.c:341
 #1: 00000000ce78bc21 (&ldata->atomic_read_lock){+.+.}, at: n_tty_read+0x232/0x1b70 drivers/tty/n_tty.c:2156
2 locks held by getty/7780:
 #0: 0000000065354e0d (&tty->ldisc_sem){++++}, at: ldsem_down_read+0x33/0x40 drivers/tty/tty_ldsem.c:341
 #1: 00000000cc7a0533 (&ldata->atomic_read_lock){+.+.}, at: n_tty_read+0x232/0x1b70 drivers/tty/n_tty.c:2156
2 locks held by getty/7781:
 #0: 00000000010d84a7 (&tty->ldisc_sem){++++}, at: ldsem_down_read+0x33/0x40 drivers/tty/tty_ldsem.c:341
 #1: 00000000617fdda7 (&ldata->atomic_read_lock){+.+.}, at: n_tty_read+0x232/0x1b70 drivers/tty/n_tty.c:2156
2 locks held by getty/7782:
 #0: 0000000069412c42 (&tty->ldisc_sem){++++}, at: ldsem_down_read+0x33/0x40 drivers/tty/tty_ldsem.c:341
 #1: 000000004134a8a6 (&ldata->atomic_read_lock){+.+.}, at: n_tty_read+0x232/0x1b70 drivers/tty/n_tty.c:2156
2 locks held by getty/7783:
 #0: 0000000070dbe92e (&tty->ldisc_sem){++++}, at: ldsem_down_read+0x33/0x40 drivers/tty/tty_ldsem.c:341
 #1: 0000000031ea0af6 (&ldata->atomic_read_lock){+.+.}, at: n_tty_read+0x232/0x1b70 drivers/tty/n_tty.c:2156
2 locks held by getty/7784:
 #0: 00000000188dedac (&tty->ldisc_sem){++++}, at: ldsem_down_read+0x33/0x40 drivers/tty/tty_ldsem.c:341
 #1: 00000000f4fd6b84 (&ldata->atomic_read_lock){+.+.}, at: n_tty_read+0x232/0x1b70 drivers/tty/n_tty.c:2156
1 lock held by syz-executor.0/8170:
 #0: 00000000fcce3432 (&sb->s_type->i_mutex_key#11){+.+.}, at: inode_lock include/linux/fs.h:769 [inline]
 #0: 00000000fcce3432 (&sb->s_type->i_mutex_key#11){+.+.}, at: __sock_release+0x89/0x2b0 net/socket.c:598

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

NMI backtrace for cpu 0
CPU: 0 PID: 1042 Comm: khungtaskd Not tainted 5.1.0-rc3+ #49
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+0x172/0x1f0 lib/dump_stack.c:113
 nmi_cpu_backtrace.cold+0x63/0xa4 lib/nmi_backtrace.c:101
 nmi_trigger_cpumask_backtrace+0x1be/0x236 lib/nmi_backtrace.c:62
 arch_trigger_cpumask_backtrace+0x14/0x20 arch/x86/kernel/apic/hw_nmi.c:38
 trigger_all_cpu_backtrace include/linux/nmi.h:146 [inline]
 check_hung_uninterruptible_tasks kernel/hung_task.c:204 [inline]
 watchdog+0x9b7/0xec0 kernel/hung_task.c:288
 kthread+0x357/0x430 kernel/kthread.c:253
 ret_from_fork+0x3a/0x50 arch/x86/entry/entry_64.S:352
Sending NMI from CPU 0 to CPUs 1:

Crashes (3):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2019/04/02 19:31 upstream 5e7a8ca31926 dfd3394d .config console log report ci-upstream-kasan-gce
2018/12/09 21:12 upstream 0844895a2e51 979179d6 .config console log report ci-upstream-kasan-gce-selinux-root
2018/05/11 17:08 net-next-old 575b65bc5bff 12c7428a .config console log report ci-upstream-net-kasan-gce
* Struck through repros no longer work on HEAD.