INFO: task hung in __do_sys_perf_event_open

[syzbot]

Hello,

syzbot found the following crash on:

HEAD commit: 3ee15ba60e6b Add linux-next specific files for 20180712
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=12712a58400000
kernel config: https://syzkaller.appspot.com/x/.config?x=fe1c3df2c7c0c81
dashboard link: https://syzkaller.appspot.com/bug?extid=84812a0271a53809c82a
compiler: gcc (GCC) 8.0.1 20180413 (experimental)
CC: [ac...@kernel.org alexander...@linux.intel.com
jo...@redhat.com linux-...@vger.kernel.org mi...@redhat.com
namh...@kernel.org pet...@infradead.org]

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+84812a...@syzkaller.appspotmail.com

team0 (unregistering): Port device team_slave_1 removed
team0 (unregistering): Port device team_slave_0 removed
bond0 (unregistering): Releasing backup interface bond_slave_1
bond0 (unregistering): Releasing backup interface bond_slave_0
bond0 (unregistering): Released all slaves
INFO: task syz-executor5:26139 blocked for more than 140 seconds.
Not tainted 4.18.0-rc4-next-20180712+ #6
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
syz-executor5 D24424 26139 4478 0x00000004
Call Trace:
context_switch kernel/sched/core.c:2853 [inline]
__schedule+0x87c/0x1ed0 kernel/sched/core.c:3501
schedule+0xfb/0x450 kernel/sched/core.c:3545
schedule_preempt_disabled+0x10/0x20 kernel/sched/core.c:3603
__mutex_lock_common kernel/locking/mutex.c:1003 [inline]
__mutex_lock+0xbf5/0x1680 kernel/locking/mutex.c:1073
mutex_lock_nested+0x16/0x20 kernel/locking/mutex.c:1088
mutex_lock_double kernel/events/core.c:10304 [inline]
__perf_event_ctx_lock_double kernel/events/core.c:10363 [inline]
__do_sys_perf_event_open+0x18da/0x2f30 kernel/events/core.c:10623
__se_sys_perf_event_open kernel/events/core.c:10383 [inline]
__x64_sys_perf_event_open+0xbe/0x150 kernel/events/core.c:10383
do_syscall_64+0x1b9/0x820 arch/x86/entry/common.c:290
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x455a79
Code: 0f 0b e8 5a 44 fd ff 0f 0b e8 c3 44 fd ff 0f 0b e8 4c 44 fd ff 0f 0b
e8 05 68 fd ff 48 8d 05 a4 9a 48 00 48 89 04 24 48 c7 44 <24> 08 1d 00 00
00 e8 8c 71 fd ff e8 37 6a fd ff 0f b6 44 24 2f 83
RSP: 002b:00007fddfaa0ec68 EFLAGS: 00000246 ORIG_RAX: 000000000000012a
RAX: ffffffffffffffda RBX: 00007fddfaa0f6d4 RCX: 0000000000455a79
RDX: 0000000000000000 RSI: ffffffffffffffff RDI: 00000000200000c0
RBP: 000000000072bea0 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000013 R11: 0000000000000246 R12: 00000000ffffffff
R13: 00000000004c07e5 R14: 00000000004d08c0 R15: 0000000000000000
INFO: task syz-executor2:26186 blocked for more than 140 seconds.
Not tainted 4.18.0-rc4-next-20180712+ #6
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
syz-executor2 D22624 26186 4481 0x80000002
Call Trace:
context_switch kernel/sched/core.c:2853 [inline]
__schedule+0x87c/0x1ed0 kernel/sched/core.c:3501
schedule+0xfb/0x450 kernel/sched/core.c:3545
schedule_preempt_disabled+0x10/0x20 kernel/sched/core.c:3603
__mutex_lock_common kernel/locking/mutex.c:1003 [inline]
__mutex_lock+0xbf5/0x1680 kernel/locking/mutex.c:1073
mutex_lock_nested+0x16/0x20 kernel/locking/mutex.c:1088
perf_event_ctx_lock_nested+0x375/0x600 kernel/events/core.c:1276
perf_event_ctx_lock kernel/events/core.c:1289 [inline]
perf_event_release_kernel+0x242/0xfc0 kernel/events/core.c:4558
perf_release+0x37/0x50 kernel/events/core.c:4647
__fput+0x35d/0x930 fs/file_table.c:252
____fput+0x15/0x20 fs/file_table.c:288
task_work_run+0x1ec/0x2a0 kernel/task_work.c:113
exit_task_work include/linux/task_work.h:22 [inline]
do_exit+0x1b08/0x2750 kernel/exit.c:869
do_group_exit+0x177/0x440 kernel/exit.c:972
get_signal+0x88e/0x1970 kernel/signal.c:2467
do_signal+0x9c/0x21c0 arch/x86/kernel/signal.c:816
exit_to_usermode_loop+0x2e5/0x380 arch/x86/entry/common.c:162
prepare_exit_to_usermode arch/x86/entry/common.c:197 [inline]
syscall_return_slowpath arch/x86/entry/common.c:268 [inline]
do_syscall_64+0x6be/0x820 arch/x86/entry/common.c:293
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x455a79
Code: 0f 0b e8 5a 44 fd ff 0f 0b e8 c3 44 fd ff 0f 0b e8 4c 44 fd ff 0f 0b
e8 05 68 fd ff 48 8d 05 a4 9a 48 00 48 89 04 24 48 c7 44 <24> 08 1d 00 00
00 e8 8c 71 fd ff e8 37 6a fd ff 0f b6 44 24 2f 83
RSP: 002b:00007fcccc789c68 EFLAGS: 00000246 ORIG_RAX: 000000000000012a
RAX: 0000000000000015 RBX: 00007fcccc78a6d4 RCX: 0000000000455a79
RDX: 0000000000000000 RSI: ffffffffffffffff RDI: 00000000200000c0
RBP: 000000000072c098 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000013 R11: 0000000000000246 R12: 00000000ffffffff
R13: 00000000004c07e5 R14: 00000000004d08c0 R15: 0000000000000003
INFO: lockdep is turned off.
NMI backtrace for cpu 0
CPU: 0 PID: 900 Comm: khungtaskd Not tainted 4.18.0-rc4-next-20180712+ #6
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+0x1c9/0x2b4 lib/dump_stack.c:113
nmi_cpu_backtrace.cold.3+0x48/0x88 lib/nmi_backtrace.c:101
nmi_trigger_cpumask_backtrace+0x151/0x192 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:144 [inline]
check_hung_uninterruptible_tasks kernel/hung_task.c:231 [inline]
watchdog+0xb81/0x10f0 kernel/hung_task.c:292
kthread+0x345/0x410 kernel/kthread.c:246
ret_from_fork+0x3a/0x50 arch/x86/entry/entry_64.S:415
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1 skipped: idling at native_safe_halt+0x6/0x10
arch/x86/include/asm/irqflags.h:54


---
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#bug-status-tracking 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.