WARNING in tracepoint_probe_register_prio (4)

[syzbot]

Hello,

syzbot found the following crash on:

HEAD commit: 50089780 selftests/bpf: Fix build of sockmap_ktls.c
git tree: bpf-next
console output: https://syzkaller.appspot.com/x/log.txt?x=13087de9e00000
kernel config: https://syzkaller.appspot.com/x/.config?x=768cc3d3e277cc16
dashboard link: https://syzkaller.appspot.com/bug?extid=1b2f76c6fb6f549f728b
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+1b2f76...@syzkaller.appspotmail.com

------------[ cut here ]------------
WARNING: CPU: 1 PID: 25402 at kernel/tracepoint.c:243 tracepoint_add_func kernel/tracepoint.c:243 [inline]
WARNING: CPU: 1 PID: 25402 at kernel/tracepoint.c:243 tracepoint_probe_register_prio+0x217/0x790 kernel/tracepoint.c:315
Kernel panic - not syncing: panic_on_warn set ...
CPU: 1 PID: 25402 Comm: syz-executor.3 Not tainted 5.6.0-rc1-syzkaller #0
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+0x197/0x210 lib/dump_stack.c:118
panic+0x2e3/0x75c kernel/panic.c:221
__warn.cold+0x2f/0x3e kernel/panic.c:582
report_bug+0x289/0x300 lib/bug.c:195
fixup_bug arch/x86/kernel/traps.c:174 [inline]
fixup_bug arch/x86/kernel/traps.c:169 [inline]
do_error_trap+0x11b/0x200 arch/x86/kernel/traps.c:267
do_invalid_op+0x37/0x50 arch/x86/kernel/traps.c:286
invalid_op+0x23/0x30 arch/x86/entry/entry_64.S:1027
RIP: 0010:tracepoint_add_func kernel/tracepoint.c:243 [inline]
RIP: 0010:tracepoint_probe_register_prio+0x217/0x790 kernel/tracepoint.c:315
Code: 48 89 f8 48 c1 e8 03 80 3c 08 00 0f 85 bf 04 00 00 48 8b 45 b8 49 3b 45 08 0f 85 21 ff ff ff 41 bd ef ff ff ff e8 d9 7b fe ff <0f> 0b e8 d2 7b fe ff 48 c7 c7 e0 5d be 89 e8 16 52 78 06 44 89 e8
RSP: 0018:ffffc90001617a68 EFLAGS: 00010212
RAX: 0000000000040000 RBX: ffffffff8aa13ec0 RCX: ffffc9001009d000
RDX: 000000000000191d RSI: ffffffff81771237 RDI: ffff888090ad3d30
RBP: ffffc90001617ac0 R08: ffff88809ae4e600 R09: fffffbfff137cbbd
R10: ffffc90001617a58 R11: ffffffff89be5de7 R12: ffff888090ad3d10
R13: 00000000ffffffef R14: 00000000ffffffff R15: ffffffff81505c80
tracepoint_probe_register+0x2b/0x40 kernel/tracepoint.c:335
trace_event_reg+0x299/0x350 kernel/trace/trace_events.c:301
perf_trace_event_reg kernel/trace/trace_event_perf.c:129 [inline]
perf_trace_event_init+0x564/0x9c0 kernel/trace/trace_event_perf.c:204
perf_trace_init+0x189/0x250 kernel/trace/trace_event_perf.c:228
perf_tp_event_init+0xa6/0x120 kernel/events/core.c:9020
perf_try_init_event+0x135/0x590 kernel/events/core.c:10471
perf_init_event kernel/events/core.c:10523 [inline]
perf_event_alloc.part.0+0x158f/0x3710 kernel/events/core.c:10803
perf_event_alloc kernel/events/core.c:11170 [inline]
__do_sys_perf_event_open+0x6f6/0x2c00 kernel/events/core.c:11286
__se_sys_perf_event_open kernel/events/core.c:11160 [inline]
__x64_sys_perf_event_open+0xbe/0x150 kernel/events/core.c:11160
do_syscall_64+0xfa/0x790 arch/x86/entry/common.c:294
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x45c449
Code: ad b6 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 b6 fb ff c3 66 2e 0f 1f 84 00 00 00 00
RSP: 002b:00007f5cb81c1c78 EFLAGS: 00000246 ORIG_RAX: 000000000000012a
RAX: ffffffffffffffda RBX: 00007f5cb81c26d4 RCX: 000000000045c449
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 000000002025c000
RBP: 000000000076bfc0 R08: 0000000000000000 R09: 0000000000000000
R10: ffffffffffffffff R11: 0000000000000246 R12: 00000000ffffffff
R13: 0000000000000812 R14: 00000000004ca890 R15: 000000000076bfcc
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]

syzbot has found a reproducer for the following issue on:

HEAD commit: 34d4ddd3 Merge tag 'linux-kselftest-5.9-rc5' of git://git...
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=13ab2b7d900000
kernel config: https://syzkaller.appspot.com/x/.config?x=8f5c353182ed6199
dashboard link: https://syzkaller.appspot.com/bug?extid=1b2f76c6fb6f549f728b
compiler: clang version 10.0.0 (https://github.com/llvm/llvm-project/ c2443155a0fb245c8f17f2c1c72b6ea391e86e81)
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=145c4735900000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12d31621900000

IMPORTANT: if you fix the issue, please add the following tag to the commit:

Reported-by: syzbot+1b2f76...@syzkaller.appspotmail.com

------------[ cut here ]------------

WARNING: CPU: 1 PID: 6978 at kernel/tracepoint.c:243 func_add kernel/tracepoint.c:147 [inline]
WARNING: CPU: 1 PID: 6978 at kernel/tracepoint.c:243 tracepoint_add_func kernel/tracepoint.c:241 [inline]
WARNING: CPU: 1 PID: 6978 at kernel/tracepoint.c:243 tracepoint_probe_register_prio+0x4ac/0x590 kernel/tracepoint.c:315

Kernel panic - not syncing: panic_on_warn set ...

CPU: 1 PID: 6978 Comm: syz-executor432 Not tainted 5.9.0-rc4-syzkaller #0

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+0x1d6/0x29e lib/dump_stack.c:118
panic+0x2c0/0x800 kernel/panic.c:231
__warn+0x227/0x250 kernel/panic.c:600
report_bug+0x1b1/0x2e0 lib/bug.c:198
handle_bug+0x42/0x80 arch/x86/kernel/traps.c:234
exc_invalid_op+0x16/0x40 arch/x86/kernel/traps.c:254
asm_exc_invalid_op+0x12/0x20 arch/x86/include/asm/idtentry.h:536
RIP: 0010:tracepoint_add_func kernel/tracepoint.c:147 [inline]
RIP: 0010:tracepoint_probe_register_prio+0x4ac/0x590 kernel/tracepoint.c:315
Code: 48 89 df e8 16 b2 1f 00 89 c5 31 ff 89 c6 e8 1b 7c fe ff 85 ed 7e 1a e8 02 78 fe ff eb 20 e8 fb 77 fe ff 49 c7 c7 ef ff ff ff <0f> 0b 44 89 fd eb 4f e8 e8 77 fe ff 48 89 df e8 30 b8 1f 00 31 ed
RSP: 0018:ffffc900055a7c38 EFLAGS: 00010293
RAX: ffffffff81768595 RBX: dffffc0000000000 RCX: ffff88808d43e1c0
RDX: 0000000000000000 RSI: 000000000000000a RDI: 000000000000000a
RBP: ffff88809d603660 R08: ffffffff8176831e R09: fffffbfff13164de
R10: fffffbfff13164de R11: 0000000000000000 R12: 000000000000000a
R13: 0000000000000003 R14: 00000000ffffffff R15: ffffffffffffffef
bpf_raw_tracepoint_open kernel/bpf/syscall.c:2741 [inline]
__do_sys_bpf+0x63ae/0x11060 kernel/bpf/syscall.c:4220
do_syscall_64+0x31/0x70 arch/x86/entry/common.c:46
entry_SYSCALL_64_after_hwframe+0x44/0xa9
RIP: 0033:0x446bd9
Code: e8 8c e7 ff ff 48 83 c4 18 c3 0f 1f 80 00 00 00 00 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 07 fc ff c3 66 2e 0f 1f 84 00 00 00 00
RSP: 002b:00007f6d31c3eda8 EFLAGS: 00000246 ORIG_RAX: 0000000000000141
RAX: ffffffffffffffda RBX: 00000000006dbc38 RCX: 0000000000446bd9
RDX: 0000000000000010 RSI: 00000000200001c0 RDI: 0000000000000011
RBP: 00000000006dbc30 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00000000006dbc3c
R13: 0000000020000100 R14: 00000000004aebc0 R15: 0000000000000064

[syzbot]

Auto-closing this bug as obsolete.
No recent activity, existing reproducers are no longer triggering the issue.