INFO: task hung in tp_perf_event_destroy

[syzbot]

Hello,

syzbot found the following crash on:

HEAD commit: 4dcb0afd ANDROID: Kbuild, LLVMLinux: allow overriding clan..
git tree: android-4.9
console output: https://syzkaller.appspot.com/x/log.txt?x=17fe5733400000
kernel config: https://syzkaller.appspot.com/x/.config?x=22a5ba9f73b6da1d
dashboard link: https://syzkaller.appspot.com/bug?extid=8a33e63c6677431b7231
compiler: gcc (GCC) 8.0.1 20180413 (experimental)

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

IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+8a33e6...@syzkaller.appspotmail.com

INFO: task syz-executor3:19874 blocked for more than 140 seconds.
Not tainted 4.9.141+ #72
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
syz-executor3 D28072 19874 2118 0x80000002
ffff88019f490000 0000000000000000 ffff8801d04db180 ffff8801da6b2f80
ffff8801db721018 ffff8801a24c7708 ffffffff82807952 0000000000000000
ffff88019f4908b0 ffffed0033e92115 00ff88019f490000 ffff8801db7218f0
Call Trace:
[<ffffffff82808e7f>] schedule+0x7f/0x1b0 kernel/sched/core.c:3553
[<ffffffff82809833>] schedule_preempt_disabled+0x13/0x20
kernel/sched/core.c:3586
[<ffffffff8280b8ad>] __mutex_lock_common kernel/locking/mutex.c:582
[inline]
[<ffffffff8280b8ad>] mutex_lock_nested+0x38d/0x900
kernel/locking/mutex.c:621
[<ffffffff81366dd8>] perf_trace_destroy+0x28/0x100
kernel/trace/trace_event_perf.c:234
[<ffffffff813c1485>] tp_perf_event_destroy+0x15/0x20
kernel/events/core.c:7769
[<ffffffff813d7882>] _free_event+0x292/0xaf0 kernel/events/core.c:4105
[<ffffffff813d8cc4>] put_event+0x24/0x30 kernel/events/core.c:4191
[<ffffffff813d905c>] perf_event_release_kernel+0x38c/0x8e0
kernel/events/core.c:4292
[<ffffffff813d95e7>] perf_release+0x37/0x50 kernel/events/core.c:4302
[<ffffffff81510293>] __fput+0x263/0x700 fs/file_table.c:208
[<ffffffff815107b5>] ____fput+0x15/0x20 fs/file_table.c:244
[<ffffffff8113dc4c>] task_work_run+0x10c/0x180 kernel/task_work.c:116
[<ffffffff810e6c4d>] exit_task_work include/linux/task_work.h:21 [inline]
[<ffffffff810e6c4d>] do_exit+0x78d/0x2a50 kernel/exit.c:833
[<ffffffff810ed3a1>] do_group_exit+0x111/0x300 kernel/exit.c:937
[<ffffffff8110eb61>] get_signal+0x4e1/0x1460 kernel/signal.c:2321
[<ffffffff81052aa5>] do_signal+0x95/0x1b00 arch/x86/kernel/signal.c:807
[<ffffffff81003e2e>] exit_to_usermode_loop+0x10e/0x150
arch/x86/entry/common.c:158
[<ffffffff81005932>] prepare_exit_to_usermode arch/x86/entry/common.c:194
[inline]
[<ffffffff81005932>] syscall_return_slowpath arch/x86/entry/common.c:263
[inline]
[<ffffffff81005932>] do_syscall_64+0x3e2/0x550 arch/x86/entry/common.c:290
[<ffffffff82817c13>] entry_SYSCALL_64_after_swapgs+0x5d/0xdb

Showing all locks held in the system:
2 locks held by khungtaskd/24:
#0: (rcu_read_lock){......}, at: [<ffffffff8131c0cc>]
check_hung_uninterruptible_tasks kernel/hung_task.c:168 [inline]
#0: (rcu_read_lock){......}, at: [<ffffffff8131c0cc>]
watchdog+0x11c/0xa20 kernel/hung_task.c:239
#1: (tasklist_lock){.+.+..}, at: [<ffffffff813fe63f>]
debug_show_all_locks+0x79/0x218 kernel/locking/lockdep.c:4336
2 locks held by getty/2034:
#0: (&tty->ldisc_sem){++++++}, at: [<ffffffff82815ce2>]
ldsem_down_read+0x32/0x40 drivers/tty/tty_ldsem.c:367
#1: (&ldata->atomic_read_lock){+.+...}, at: [<ffffffff81d376f2>]
n_tty_read+0x202/0x16e0 drivers/tty/n_tty.c:2142
1 lock held by syz-executor3/19874:
#0: (event_mutex){+.+.+.}, at: [<ffffffff81366dd8>]
perf_trace_destroy+0x28/0x100 kernel/trace/trace_event_perf.c:234
1 lock held by syz-executor3/19882:
#0: (event_mutex){+.+.+.}, at: [<ffffffff81366dd8>]
perf_trace_destroy+0x28/0x100 kernel/trace/trace_event_perf.c:234
1 lock held by syz-executor3/19887:
#0: (event_mutex){+.+.+.}, at: [<ffffffff81366dd8>]
perf_trace_destroy+0x28/0x100 kernel/trace/trace_event_perf.c:234
1 lock held by syz-executor3/19894:
#0: (event_mutex){+.+.+.}, at: [<ffffffff81366dd8>]
perf_trace_destroy+0x28/0x100 kernel/trace/trace_event_perf.c:234
1 lock held by syz-executor3/19905:
#0: (event_mutex){+.+.+.}, at: [<ffffffff81366dd8>]
perf_trace_destroy+0x28/0x100 kernel/trace/trace_event_perf.c:234
1 lock held by syz-executor3/19908:
#0: (event_mutex){+.+.+.}, at: [<ffffffff81366dd8>]
perf_trace_destroy+0x28/0x100 kernel/trace/trace_event_perf.c:234
1 lock held by syz-executor3/22772:
#0: (event_mutex){+.+.+.}, at: [<ffffffff81366dd8>]
perf_trace_destroy+0x28/0x100 kernel/trace/trace_event_perf.c:234

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

NMI backtrace for cpu 1
CPU: 1 PID: 24 Comm: khungtaskd Not tainted 4.9.141+ #72
ffff8801d9907d08 ffffffff81b43209 0000000000000000 0000000000000001
0000000000000001 0000000000000001 ffffffff810983b0 ffff8801d9907d40
ffffffff81b4e319 0000000000000001 0000000000000000 0000000000000003
Call Trace:
[<ffffffff81b43209>] __dump_stack lib/dump_stack.c:15 [inline]
[<ffffffff81b43209>] dump_stack+0xc1/0x128 lib/dump_stack.c:51
[<ffffffff81b4e319>] nmi_cpu_backtrace.cold.0+0x48/0x87
lib/nmi_backtrace.c:99
[<ffffffff81b4e2ac>] nmi_trigger_cpumask_backtrace+0x12c/0x151
lib/nmi_backtrace.c:60
[<ffffffff810984b4>] arch_trigger_cpumask_backtrace+0x14/0x20
arch/x86/kernel/apic/hw_nmi.c:37
[<ffffffff8131c65d>] trigger_all_cpu_backtrace include/linux/nmi.h:58
[inline]
[<ffffffff8131c65d>] check_hung_task kernel/hung_task.c:125 [inline]
[<ffffffff8131c65d>] check_hung_uninterruptible_tasks
kernel/hung_task.c:182 [inline]
[<ffffffff8131c65d>] watchdog+0x6ad/0xa20 kernel/hung_task.c:239
[<ffffffff81142c3d>] kthread+0x26d/0x300 kernel/kthread.c:211
[<ffffffff82817ddc>] ret_from_fork+0x5c/0x70 arch/x86/entry/entry_64.S:373
Sending NMI from CPU 1 to CPUs 0:
NMI backtrace for cpu 0 skipped: idling at pc 0xffffffff82816826


---
This bug 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 bug report. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

[syzbot]

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