[syzbot] WARNING in __perf_event_overflow

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 88619e77b33d net: stmmac: rk3588: Allow multiple gmac cont..
git tree: bpf
console+strace: https://syzkaller.appspot.com/x/log.txt?x=11842046880000
kernel config: https://syzkaller.appspot.com/x/.config?x=a66c6c673fb555e8
dashboard link: https://syzkaller.appspot.com/bug?extid=589d998651a580e6135d
compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11eabcea880000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=10f7e632880000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/f8435d5c2c21/disk-88619e77.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/551d8a013e81/vmlinux-88619e77.xz
kernel image: https://storage.googleapis.com/syzbot-assets/7d3f5c29064d/bzImage-88619e77.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+589d99...@syzkaller.appspotmail.com

------------[ cut here ]------------
WARNING: CPU: 0 PID: 3607 at kernel/events/core.c:9313 __perf_event_overflow+0x498/0x540 kernel/events/core.c:9313
Modules linked in:
CPU: 0 PID: 3607 Comm: syz-executor100 Not tainted 6.1.0-rc2-syzkaller-00073-g88619e77b33d #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/11/2022
RIP: 0010:__perf_event_overflow+0x498/0x540 kernel/events/core.c:9313
Code: 80 3c 02 00 0f 85 b2 00 00 00 48 8b 83 20 02 00 00 48 ff 80 b8 01 00 00 e9 5b fe ff ff 45 31 f6 e9 a2 fd ff ff e8 f8 ae dd ff <0f> 0b e9 47 fe ff ff 4c 89 e7 e8 39 ff 29 00 e9 b2 fb ff ff e8 0f
RSP: 0000:ffffc90003c4fb00 EFLAGS: 00010046
RAX: 0000000080010000 RBX: ffff888011a891d0 RCX: 0000000000000000
RDX: ffff88801a4d57c0 RSI: ffffffff819eecc8 RDI: 0000000000000001
RBP: ffffc90003c4fb80 R08: 0000000000000001 R09: 0000000000000000
R10: 0000000000000020 R11: 0000000000000001 R12: 0000000000000020
R13: ffff888011a895f4 R14: 0000000000000000 R15: 0000000000000000
FS: 0000555555a8e300(0000) GS:ffff8880b9a00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000020000648 CR3: 000000007c988000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
perf_swevent_hrtimer+0x34f/0x3c0 kernel/events/core.c:10729
__run_hrtimer kernel/time/hrtimer.c:1685 [inline]
__hrtimer_run_queues+0x1c6/0xfb0 kernel/time/hrtimer.c:1749
hrtimer_interrupt+0x31c/0x790 kernel/time/hrtimer.c:1811
local_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1096 [inline]
__sysvec_apic_timer_interrupt+0x17c/0x640 arch/x86/kernel/apic/apic.c:1113
sysvec_apic_timer_interrupt+0x40/0xc0 arch/x86/kernel/apic/apic.c:1107
asm_sysvec_apic_timer_interrupt+0x16/0x20 arch/x86/include/asm/idtentry.h:649
RIP: 0033:0x7f74350afae5
Code: 00 c7 04 25 b0 06 00 20 00 00 00 00 c7 04 25 b4 06 00 20 00 00 00 00 48 c7 04 25 b8 06 00 20 4f ff ff ff e8 ed e2 03 00 31 ff <e8> a6 75 00 00 66 0f 1f 44 00 00 41 57 41 56 41 55 41 54 55 53 48
RSP: 002b:00007fffceb2b0e0 EFLAGS: 00000246
RAX: 0000000000000003 RBX: 000000000000a025 RCX: 00007f74350edde9
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: 0000000000000000 R08: 0000000000000008 R09: 00007fffceb2b278
R10: 00000000ffffffff R11: 0000000000000246 R12: 00007fffceb2b0ec
R13: 431bde82d7b634db R14: 0000000000000000 R15: 0000000000000000
</TASK>


---
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 can test patches for this issue, for details see:
https://goo.gl/tpsmEJ#testing-patches

[Marco Elver]

Proposed fix for this is:
https://lore.kernel.org/all/20221031093513....@google.com/

[syzbot]

syzbot has bisected this issue to:

commit c1d050b0d169fd60c8acef157db53bd4e3141799
Author: Yishai Hadas <yis...@nvidia.com>
Date: Thu Sep 8 18:34:45 2022 +0000

vfio/mlx5: Create and destroy page tracker object

bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=136eb2da880000
start commit: 88619e77b33d net: stmmac: rk3588: Allow multiple gmac cont..
git tree: bpf
final oops: https://syzkaller.appspot.com/x/report.txt?x=10eeb2da880000
console output: https://syzkaller.appspot.com/x/log.txt?x=176eb2da880000

kernel config: https://syzkaller.appspot.com/x/.config?x=a66c6c673fb555e8
dashboard link: https://syzkaller.appspot.com/bug?extid=589d998651a580e6135d

syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11eabcea880000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=10f7e632880000

Reported-by: syzbot+589d99...@syzkaller.appspotmail.com
Fixes: c1d050b0d169 ("vfio/mlx5: Create and destroy page tracker object")

For information about bisection process see: https://goo.gl/tpsmEJ#bisection

[Marco Elver]

The bisection is wrong - see
https://lore.kernel.org/all/20221031093513....@google.com/