general protection fault in msr_event_init

[syzbot]

Hello,

syzbot found the following crash on:

HEAD commit: 7cc2a8ea Merge tag 'block-5.8-2020-07-01' of git://git.ker..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=108d022f100000
kernel config: https://syzkaller.appspot.com/x/.config?x=7be693511b29b338
dashboard link: https://syzkaller.appspot.com/bug?extid=20a5ec9650d57bd7e4f5
compiler: gcc (GCC) 10.1.0-syz 20200507
CC: [ac...@kernel.org alexander...@linux.intel.com b...@alien8.de h...@zytor.com jo...@redhat.com linux-...@vger.kernel.org mark.r...@arm.com mi...@redhat.com namh...@kernel.org pet...@infradead.org tg...@linutronix.de x...@kernel.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+20a5ec...@syzkaller.appspotmail.com

general protection fault, probably for non-canonical address 0xdffffc0000000000: 0000 [#1] PREEMPT SMP KASAN
KASAN: null-ptr-deref in range [0x0000000000000000-0x0000000000000007]
CPU: 1 PID: 21572 Comm: syz-executor.1 Not tainted 5.8.0-rc3-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
RIP: 0010:msr_event_init+0x0/0x2a0 arch/x86/events/msr.c:190
Code: d3 fe ff ff e8 61 fb b0 00 e9 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 <00> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
RSP: 0018:ffffc900055b7c88 EFLAGS: 00010246
RAX: dffffc0000000000 RBX: ffffffff89a951c0 RCX: ffffc9000453c000
RDX: 1ffffffff1352a46 RSI: ffffffff818d21ed RDI: ffff888087181000
RBP: ffff888087181000 R08: 0000000000000001 R09: ffff888065e78d48
R10: 0000000000000000 R11: 0000000000000000 R12: ffff888087181000
R13: ffffffff89a951d0 R14: 0000000000000001 R15: ffffffff89a951c0
FS: 00007f08a466c700(0000) GS:ffff8880ae700000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00000000005166a0 CR3: 00000000a6256000 CR4: 00000000001426e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
perf_try_init_event+0x12a/0x560 kernel/events/core.c:10782
perf_init_event kernel/events/core.c:10847 [inline]
perf_event_alloc.part.0+0x1bdb/0x36f0 kernel/events/core.c:11110
perf_event_alloc kernel/events/core.c:11489 [inline]
__do_sys_perf_event_open+0x72c/0x2b50 kernel/events/core.c:11605
do_syscall_64+0x60/0xe0 arch/x86/entry/common.c:359
entry_SYSCALL_64_after_hwframe+0x44/0xa9
RIP: 0033:0x45cb29
Code: Bad RIP value.
RSP: 002b:00007f08a466bc78 EFLAGS: 00000246 ORIG_RAX: 000000000000012a
RAX: ffffffffffffffda RBX: 00000000004fa720 RCX: 000000000045cb29
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000020000080
RBP: 000000000078bf00 R08: 0000000000000000 R09: 0000000000000000
R10: ffffffffffffffff R11: 0000000000000246 R12: 00000000ffffffff
R13: 0000000000000842 R14: 00000000004cb34b R15: 00007f08a466c6d4
Modules linked in:
---[ end trace a02120299fa9bcae ]---
RIP: 0010:msr_event_init+0x0/0x2a0 arch/x86/events/msr.c:190
Code: d3 fe ff ff e8 61 fb b0 00 e9 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 <00> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
RSP: 0018:ffffc900055b7c88 EFLAGS: 00010246
RAX: dffffc0000000000 RBX: ffffffff89a951c0 RCX: ffffc9000453c000
RDX: 1ffffffff1352a46 RSI: ffffffff818d21ed RDI: ffff888087181000
RBP: ffff888087181000 R08: 0000000000000001 R09: ffff888065e78d48
R10: 0000000000000000 R11: 0000000000000000 R12: ffff888087181000
R13: ffffffff89a951d0 R14: 0000000000000001 R15: ffffffff89a951c0
FS: 00007f08a466c700(0000) GS:ffff8880ae700000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000768000 CR3: 00000000a6256000 CR4: 00000000001426e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400


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