general protection fault in perf_cgroup_switch

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: f25a5481af12 Merge tag 'libnvdimm-fixes-5.15-rc8' of git:/..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1593b4ecb00000
kernel config: https://syzkaller.appspot.com/x/.config?x=6a38b8c18ca03c4e
dashboard link: https://syzkaller.appspot.com/bug?extid=0036d1a297db4d1c8d74
compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
userspace arch: i386
CC: [ac...@kernel.org alexander...@linux.intel.com and...@kernel.org a...@kernel.org b...@vger.kernel.org dan...@iogearbox.net john.fa...@gmail.com jo...@redhat.com ka...@fb.com kps...@kernel.org linux-...@vger.kernel.org linux-pe...@vger.kernel.org mark.r...@arm.com mi...@redhat.com namh...@kernel.org net...@vger.kernel.org pet...@infradead.org songliu...@fb.com y...@fb.com]

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+0036d1...@syzkaller.appspotmail.com

general protection fault, probably for non-canonical address 0xfbd59c0000000007: 0000 [#1] PREEMPT SMP KASAN
KASAN: maybe wild-memory-access in range [0xdead000000000038-0xdead00000000003f]
CPU: 0 PID: 3678 Comm: syz-executor.3 Not tainted 5.15.0-rc7-syzkaller #0
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.14.0-2 04/01/2014
RIP: 0010:perf_cgroup_switch+0x31d/0x8c0 kernel/events/core.c:817
Code: 83 50 02 00 00 48 39 44 24 10 48 8d 98 b0 fd ff ff 0f 84 03 03 00 00 e8 d1 ad df ff 48 8d bb 8c 01 00 00 48 89 f8 48 c1 e8 03 <0f> b6 14 28 48 89 f8 83 e0 07 83 c0 03 38 d0 7c 08 84 d2 0f 85 c9
RSP: 0018:ffffc90001467920 EFLAGS: 00010803
RAX: 1bd5a00000000007 RBX: deacfffffffffeb0 RCX: 0000000000000000
RDX: ffff888013e63900 RSI: ffffffff81973f4f RDI: dead00000000003c
RBP: dffffc0000000000 R08: 0000000000000000 R09: ffff88802ca37a0b
R10: ffffed1005946f41 R11: 0000000000000000 R12: 0000000000000000
R13: ffff88802ca37a08 R14: ffffffff8ba4d180 R15: ffff88802ca36740
FS: 0000000000000000(0000) GS:ffff88802ca00000(0063) knlGS:0000000057f61380
CS: 0010 DS: 002b ES: 002b CR0: 0000000080050033
CR2: 00000000f4551b18 CR3: 0000000075019000 CR4: 0000000000150ef0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
perf_cgroup_sched_in kernel/events/core.c:898 [inline]
__perf_event_task_sched_in+0x3a6/0xae0 kernel/events/core.c:3920
perf_event_task_sched_in include/linux/perf_event.h:1208 [inline]
finish_task_switch.isra.0+0x6a7/0xb80 kernel/sched/core.c:4809
context_switch kernel/sched/core.c:4943 [inline]
__schedule+0xb4c/0x5960 kernel/sched/core.c:6287
schedule+0xd3/0x270 kernel/sched/core.c:6366
freezable_schedule include/linux/freezer.h:172 [inline]
do_nanosleep+0x24e/0x690 kernel/time/hrtimer.c:2044
hrtimer_nanosleep+0x1f9/0x4a0 kernel/time/hrtimer.c:2097
common_nsleep+0xa2/0xc0 kernel/time/posix-timers.c:1227
__do_sys_clock_nanosleep kernel/time/posix-timers.c:1267 [inline]
__se_sys_clock_nanosleep kernel/time/posix-timers.c:1245 [inline]
__ia32_sys_clock_nanosleep+0x2f4/0x430 kernel/time/posix-timers.c:1245
do_syscall_32_irqs_on arch/x86/entry/common.c:112 [inline]
__do_fast_syscall_32+0x65/0xf0 arch/x86/entry/common.c:178
do_fast_syscall_32+0x2f/0x70 arch/x86/entry/common.c:203
entry_SYSENTER_compat_after_hwframe+0x4d/0x5c
RIP: 0023:0xf6eb2549
Code: 03 74 c0 01 10 05 03 74 b8 01 10 06 03 74 b4 01 10 07 03 74 b0 01 10 08 03 74 d8 01 00 00 00 00 00 51 52 55 89 e5 0f 34 cd 80 <5d> 5a 59 c3 90 90 90 90 8d b4 26 00 00 00 00 8d b4 26 00 00 00 00
RSP: 002b:00000000ffc5e4c0 EFLAGS: 00000282 ORIG_RAX: 0000000000000197
RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 0000000000000000
RDX: 00000000ffc5e53c RSI: 00000000ffc5e54c RDI: 00000000ffc5e53c
RBP: 00000000ffc5e54c R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000
R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
Modules linked in:
---[ end trace fb252b2af5fa947c ]---
RIP: 0010:perf_cgroup_switch+0x31d/0x8c0 kernel/events/core.c:817
Code: 83 50 02 00 00 48 39 44 24 10 48 8d 98 b0 fd ff ff 0f 84 03 03 00 00 e8 d1 ad df ff 48 8d bb 8c 01 00 00 48 89 f8 48 c1 e8 03 <0f> b6 14 28 48 89 f8 83 e0 07 83 c0 03 38 d0 7c 08 84 d2 0f 85 c9
RSP: 0018:ffffc90001467920 EFLAGS: 00010803
RAX: 1bd5a00000000007 RBX: deacfffffffffeb0 RCX: 0000000000000000
RDX: ffff888013e63900 RSI: ffffffff81973f4f RDI: dead00000000003c
RBP: dffffc0000000000 R08: 0000000000000000 R09: ffff88802ca37a0b
R10: ffffed1005946f41 R11: 0000000000000000 R12: 0000000000000000
R13: ffff88802ca37a08 R14: ffffffff8ba4d180 R15: ffff88802ca36740
FS: 0000000000000000(0000) GS:ffff88802ca00000(0063) knlGS:0000000057f61380
CS: 0010 DS: 002b ES: 002b CR0: 0000000080050033
CR2: 00000000f4551b18 CR3: 0000000075019000 CR4: 0000000000150ef0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
----------------
Code disassembly (best guess):
0: 83 50 02 00 adcl $0x0,0x2(%rax)
4: 00 48 39 add %cl,0x39(%rax)
7: 44 24 10 rex.R and $0x10,%al
a: 48 8d 98 b0 fd ff ff lea -0x250(%rax),%rbx
11: 0f 84 03 03 00 00 je 0x31a
17: e8 d1 ad df ff callq 0xffdfaded
1c: 48 8d bb 8c 01 00 00 lea 0x18c(%rbx),%rdi
23: 48 89 f8 mov %rdi,%rax
26: 48 c1 e8 03 shr $0x3,%rax
* 2a: 0f b6 14 28 movzbl (%rax,%rbp,1),%edx <-- trapping instruction
2e: 48 89 f8 mov %rdi,%rax
31: 83 e0 07 and $0x7,%eax
34: 83 c0 03 add $0x3,%eax
37: 38 d0 cmp %dl,%al
39: 7c 08 jl 0x43
3b: 84 d2 test %dl,%dl
3d: 0f .byte 0xf
3e: 85 c9 test %ecx,%ecx


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

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