WARNING in tracepoint_probe_register_prio

[syzbot]

Hello,

syzbot found the following crash on:

HEAD commit: c98875d9 Linux 4.19.36
git tree: linux-4.19.y
console output: https://syzkaller.appspot.com/x/log.txt?x=11041d80a00000
kernel config: https://syzkaller.appspot.com/x/.config?x=5e40ac5fbcc6366d
dashboard link: https://syzkaller.appspot.com/bug?extid=d0f9dcb9810e560b7b33
compiler: gcc (GCC) 9.0.0 20181231 (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+d0f9dc...@syzkaller.appspotmail.com

WARNING: CPU: 1 PID: 23968 at kernel/tracepoint.c:256 tracepoint_add_func
kernel/tracepoint.c:256 [inline]
WARNING: CPU: 1 PID: 23968 at kernel/tracepoint.c:256
tracepoint_probe_register_prio+0x217/0x7b0 kernel/tracepoint.c:328
Kernel panic - not syncing: panic_on_warn set ...

CPU: 1 PID: 23968 Comm: syz-executor.3 Not tainted 4.19.36 #4
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+0x172/0x1f0 lib/dump_stack.c:113
panic+0x263/0x51d kernel/panic.c:185
__warn.cold+0x20/0x54 kernel/panic.c:540
report_bug+0x263/0x2b0 lib/bug.c:186
fixup_bug arch/x86/kernel/traps.c:178 [inline]
fixup_bug arch/x86/kernel/traps.c:173 [inline]
do_error_trap+0x204/0x360 arch/x86/kernel/traps.c:296
do_invalid_op+0x1b/0x20 arch/x86/kernel/traps.c:316
invalid_op+0x14/0x20 arch/x86/entry/entry_64.S:997
RIP: 0010:tracepoint_add_func kernel/tracepoint.c:256 [inline]
RIP: 0010:tracepoint_probe_register_prio+0x217/0x7b0 kernel/tracepoint.c:328
Code: 48 89 f8 48 c1 e8 03 80 3c 08 00 0f 85 cf 04 00 00 48 8b 45 b8 49 3b
45 08 0f 85 21 ff ff ff 41 bd ef ff ff ff e8 69 b6 fe ff <0f> 0b e8 62 b6
fe ff 48 c7 c7 e0 51 7d 88 e8 a6 4e 81 05 44 89 e8
RSP: 0018:ffff888068917a88 EFLAGS: 00010212
RAX: 0000000000040000 RBX: ffffffff89362a60 RCX: ffffc90012b8d000
RDX: 00000000000012c9 RSI: ffffffff816c8ea7 RDI: ffff8880949ca5b0
RBP: ffff888068917ae0 R08: ffff88805711a600 R09: fffffbfff10faa3d
R10: ffff888068917a78 R11: ffffffff887d51e7 R12: ffff8880949ca590
R13: 00000000ffffffef R14: 00000000ffffffff R15: ffffffff814922f0
tracepoint_probe_register+0x2b/0x40 kernel/tracepoint.c:348
trace_event_reg+0x299/0x350 kernel/trace/trace_events.c:306
perf_trace_event_reg kernel/trace/trace_event_perf.c:124 [inline]
perf_trace_event_init+0x500/0x990 kernel/trace/trace_event_perf.c:199
perf_trace_init+0x189/0x250 kernel/trace/trace_event_perf.c:223
perf_tp_event_init+0xa6/0x120 kernel/events/core.c:8362
perf_try_init_event+0x137/0x2f0 kernel/events/core.c:9759
perf_init_event kernel/events/core.c:9797 [inline]
perf_event_alloc.part.0+0xf98/0x2e00 kernel/events/core.c:10063
perf_event_alloc kernel/events/core.c:10419 [inline]
__do_sys_perf_event_open+0x842/0x2730 kernel/events/core.c:10520
__se_sys_perf_event_open kernel/events/core.c:10409 [inline]
__x64_sys_perf_event_open+0xbe/0x150 kernel/events/core.c:10409
do_syscall_64+0x103/0x610 arch/x86/entry/common.c:290
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x458c29
Code: ad b8 fb ff c3 66 2e 0f 1f 84 00 00 00 00 00 66 90 48 89 f8 48 89 f7
48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff
ff 0f 83 7b b8 fb ff c3 66 2e 0f 1f 84 00 00 00 00
RSP: 002b:00007f733aca3c78 EFLAGS: 00000246 ORIG_RAX: 000000000000012a
RAX: ffffffffffffffda RBX: 0000000000000005 RCX: 0000000000458c29
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 000000002025c000
RBP: 000000000073bf00 R08: 0000000000000000 R09: 0000000000000000
R10: ffffffffffffffff R11: 0000000000000246 R12: 00007f733aca46d4
R13: 00000000004c54b5 R14: 00000000004d9698 R15: 00000000ffffffff
Kernel Offset: disabled
Rebooting in 86400 seconds..


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