WARNING in tracepoint_add_func

29 views
Skip to first unread message

syzbot

unread,
Jun 28, 2020, 7:29:17 AM6/28/20
to linux-...@vger.kernel.org, mathieu....@polymtl.ca, mi...@elte.hu, net...@vger.kernel.org, ros...@goodmis.org, syzkall...@googlegroups.com
Hello,

syzbot found the following crash on:

HEAD commit: 7a64135f libbpf: Adjust SEC short cut for expected attach ..
git tree: bpf
console output: https://syzkaller.appspot.com/x/log.txt?x=142782e3100000
kernel config: https://syzkaller.appspot.com/x/.config?x=dcc6334acae363d4
dashboard link: https://syzkaller.appspot.com/bug?extid=721aa903751db87aa244
compiler: gcc (GCC) 10.1.0-syz 20200507

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+721aa9...@syzkaller.appspotmail.com

------------[ cut here ]------------
WARNING: CPU: 1 PID: 16762 at kernel/tracepoint.c:243 tracepoint_add_func+0x254/0x880 kernel/tracepoint.c:243
Kernel panic - not syncing: panic_on_warn set ...
CPU: 1 PID: 16762 Comm: syz-executor.4 Not tainted 5.8.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+0x18f/0x20d lib/dump_stack.c:118
panic+0x2e3/0x75c kernel/panic.c:231
__warn.cold+0x20/0x45 kernel/panic.c:600
report_bug+0x1bd/0x210 lib/bug.c:198
exc_invalid_op+0x24d/0x400 arch/x86/kernel/traps.c:235
asm_exc_invalid_op+0x12/0x20 arch/x86/include/asm/idtentry.h:563
RIP: 0010:tracepoint_add_func+0x254/0x880 kernel/tracepoint.c:243
Code: 44 24 20 48 8b 5b 08 80 38 00 0f 85 6b 05 00 00 48 8b 44 24 08 48 3b 58 08 0f 85 2d ff ff ff 41 bc ef ff ff ff e8 4c 78 fe ff <0f> 0b e8 45 78 fe ff 44 89 e0 48 83 c4 38 5b 5d 41 5c 41 5d 41 5e
RSP: 0018:ffffc90001497a98 EFLAGS: 00010216
RAX: 000000000000199a RBX: ffffffff89b99040 RCX: ffffc90011df4000
RDX: 0000000000040000 RSI: ffffffff8174d824 RDI: ffff8880979adb30
RBP: ffffffff814f1b80 R08: 0000000000000000 R09: ffffffff89bf9867
R10: 000000000000000a R11: 0000000000000000 R12: 00000000ffffffef
R13: 0000000000000001 R14: dffffc0000000000 R15: ffff8880979adb10
tracepoint_probe_register_prio kernel/tracepoint.c:315 [inline]
tracepoint_probe_register+0x9c/0xe0 kernel/tracepoint.c:335
trace_event_reg+0x28f/0x350 kernel/trace/trace_events.c:304
perf_trace_event_reg kernel/trace/trace_event_perf.c:129 [inline]
perf_trace_event_init+0x532/0x9a0 kernel/trace/trace_event_perf.c:204
perf_trace_init+0x176/0x240 kernel/trace/trace_event_perf.c:228
perf_tp_event_init+0xa2/0x120 kernel/events/core.c:9330
perf_try_init_event+0x12a/0x560 kernel/events/core.c:10782
perf_init_event kernel/events/core.c:10834 [inline]
perf_event_alloc.part.0+0xdee/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:0x45cb19
Code: Bad RIP value.
RSP: 002b:00007f2d99608c78 EFLAGS: 00000246 ORIG_RAX: 000000000000012a
RAX: ffffffffffffffda RBX: 00000000004fa640 RCX: 000000000045cb19
RDX: 0000000000000000 RSI: ffffffffffffffff RDI: 0000000020000100
RBP: 000000000078bf00 R08: 0000000000000000 R09: 0000000000000000
R10: ffffffffffffffff R11: 0000000000000246 R12: 00000000ffffffff
R13: 0000000000000841 R14: 00000000004cb320 R15: 00007f2d996096d4
Kernel Offset: disabled


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

Steven Rostedt

unread,
Jun 29, 2020, 8:56:11 AM6/29/20
to syzbot, linux-...@vger.kernel.org, mathieu....@polymtl.ca, mi...@elte.hu, net...@vger.kernel.org, syzkall...@googlegroups.com, Peter Zijlstra, Frederic Weisbecker

Cc'd Frederic and Peter.

-- Steve

syzbot

unread,
Sep 10, 2020, 5:44:17 AM9/10/20
to fred...@kernel.org, linux-...@vger.kernel.org, mathieu....@polymtl.ca, mi...@elte.hu, net...@vger.kernel.org, pet...@infradead.org, ros...@goodmis.org, syzkall...@googlegroups.com
syzbot has found a reproducer for the following issue on:

HEAD commit: 746f534a tools/libbpf: Avoid counting local symbols in ABI..
git tree: bpf
console output: https://syzkaller.appspot.com/x/log.txt?x=1317f559900000
kernel config: https://syzkaller.appspot.com/x/.config?x=a0437fdd630bee11
dashboard link: https://syzkaller.appspot.com/bug?extid=721aa903751db87aa244
compiler: gcc (GCC) 10.1.0-syz 20200507
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=128ff37d900000

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

------------[ cut here ]------------
WARNING: CPU: 1 PID: 7451 at kernel/tracepoint.c:243 tracepoint_add_func+0x254/0x880 kernel/tracepoint.c:243
Kernel panic - not syncing: panic_on_warn set ...
CPU: 0 PID: 7451 Comm: syz-executor.0 Not tainted 5.9.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+0x18f/0x20d lib/dump_stack.c:118
panic+0x2e3/0x75c kernel/panic.c:231
__warn.cold+0x20/0x4a kernel/panic.c:600
report_bug+0x1bd/0x210 lib/bug.c:198
handle_bug+0x38/0x90 arch/x86/kernel/traps.c:234
exc_invalid_op+0x14/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+0x254/0x880 kernel/tracepoint.c:243
Code: 44 24 20 48 8b 5b 08 80 38 00 0f 85 6b 05 00 00 48 8b 44 24 08 48 3b 58 08 0f 85 2d ff ff ff 41 bc ef ff ff ff e8 7c 68 fe ff <0f> 0b e8 75 68 fe ff 44 89 e0 48 83 c4 38 5b 5d 41 5c 41 5d 41 5e
RSP: 0018:ffffc900056e7ac0 EFLAGS: 00010293
RAX: 0000000000000000 RBX: ffffc90000e76000 RCX: ffffffff8175d632
RDX: ffff8880a85ae5c0 RSI: ffffffff8175d694 RDI: ffff8880942a1798
RBP: ffffffff82101830 R08: 0000000000000000 R09: ffffffff89c13687
R10: 000000000000000a R11: 0000000000000000 R12: 00000000ffffffef
R13: 0000000000000000 R14: dffffc0000000000 R15: ffff8880942a1790
tracepoint_probe_register_prio kernel/tracepoint.c:315 [inline]
tracepoint_probe_register+0x9c/0xe0 kernel/tracepoint.c:335
__bpf_probe_register kernel/trace/bpf_trace.c:1950 [inline]
bpf_probe_register+0x16c/0x1d0 kernel/trace/bpf_trace.c:1955
bpf_raw_tracepoint_open+0x34e/0xb20 kernel/bpf/syscall.c:2741
__do_sys_bpf+0x1336/0x4c20 kernel/bpf/syscall.c:4220
do_syscall_64+0x2d/0x70 arch/x86/entry/common.c:46
entry_SYSCALL_64_after_hwframe+0x44/0xa9
RIP: 0033:0x45d5b9
Code: 5d b4 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 2b b4 fb ff c3 66 2e 0f 1f 84 00 00 00 00
RSP: 002b:00007f23d5b85c78 EFLAGS: 00000246 ORIG_RAX: 0000000000000141
RAX: ffffffffffffffda RBX: 0000000000001800 RCX: 000000000045d5b9
RDX: 0000000000000010 RSI: 0000000020000080 RDI: 0000000000000011
RBP: 000000000118cf80 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 000000000118cf4c
R13: 00007fffab077bbf R14: 00007f23d5b869c0 R15: 000000000118cf4c
Kernel Offset: disabled
Rebooting in 86400 seconds..

syzbot

unread,
Sep 13, 2020, 3:16:05 PM9/13/20
to cor...@lwn.net, da...@davemloft.net, dsa...@gmail.com, fred...@kernel.org, linu...@vger.kernel.org, linux-...@vger.kernel.org, mathieu....@polymtl.ca, mi...@elte.hu, net...@vger.kernel.org, pet...@infradead.org, ros...@goodmis.org, syzkall...@googlegroups.com
syzbot has bisected this issue to:

commit 58956317c8de52009d1a38a721474c24aef74fe7
Author: David Ahern <dsa...@gmail.com>
Date: Fri Dec 7 20:24:57 2018 +0000

neighbor: Improve garbage collection

bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=146ba853900000
start commit: 746f534a tools/libbpf: Avoid counting local symbols in ABI..
git tree: bpf
final oops: https://syzkaller.appspot.com/x/report.txt?x=166ba853900000
console output: https://syzkaller.appspot.com/x/log.txt?x=126ba853900000
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=128ff37d900000

Reported-by: syzbot+721aa9...@syzkaller.appspotmail.com
Fixes: 58956317c8de ("neighbor: Improve garbage collection")

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

syzbot

unread,
Sep 21, 2020, 12:56:17 AM9/21/20
to cor...@lwn.net, da...@davemloft.net, dsa...@gmail.com, fred...@kernel.org, linu...@vger.kernel.org, linux-...@vger.kernel.org, mathieu....@polymtl.ca, mi...@elte.hu, net...@vger.kernel.org, pet...@infradead.org, ros...@goodmis.org, syzkall...@googlegroups.com
syzbot has found a reproducer for the following issue on:

HEAD commit: 325d0eab Merge branch 'akpm' (patches from Andrew)
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=16992c81900000
kernel config: https://syzkaller.appspot.com/x/.config?x=b12e84189082991c
dashboard link: https://syzkaller.appspot.com/bug?extid=721aa903751db87aa244
compiler: gcc (GCC) 10.1.0-syz 20200507
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=17c797b5900000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=10569c03900000

The issue was bisected to:

commit 58956317c8de52009d1a38a721474c24aef74fe7
Author: David Ahern <dsa...@gmail.com>
Date: Fri Dec 7 20:24:57 2018 +0000

neighbor: Improve garbage collection

bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=146ba853900000
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+721aa9...@syzkaller.appspotmail.com
Fixes: 58956317c8de ("neighbor: Improve garbage collection")

------------[ cut here ]------------
WARNING: CPU: 1 PID: 6872 at kernel/tracepoint.c:243 tracepoint_add_func+0x254/0x880 kernel/tracepoint.c:243
Kernel panic - not syncing: panic_on_warn set ...
CPU: 1 PID: 6872 Comm: syz-executor482 Not tainted 5.9.0-rc5-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+0x198/0x1fd lib/dump_stack.c:118
panic+0x382/0x7fb kernel/panic.c:231
__warn.cold+0x20/0x4b kernel/panic.c:600
report_bug+0x1bd/0x210 lib/bug.c:198
handle_bug+0x38/0x90 arch/x86/kernel/traps.c:234
exc_invalid_op+0x14/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+0x254/0x880 kernel/tracepoint.c:243
Code: 44 24 20 48 8b 5b 08 80 38 00 0f 85 6b 05 00 00 48 8b 44 24 08 48 3b 58 08 0f 85 2d ff ff ff 41 bc ef ff ff ff e8 ec 62 fe ff <0f> 0b e8 e5 62 fe ff 44 89 e0 48 83 c4 38 5b 5d 41 5c 41 5d 41 5e
RSP: 0000:ffffc900060f7ac0 EFLAGS: 00010293
RAX: 0000000000000000 RBX: ffffc90000e76000 RCX: ffffffff8177dc72
RDX: ffff888096766000 RSI: ffffffff8177dcd4 RDI: ffff8880a6b2ec48
RBP: ffffffff8213fae0 R08: 0000000000000000 R09: ffffffff8a0c176b
R10: 000000000000000a R11: 0000000000000000 R12: 00000000ffffffef
R13: 0000000000000002 R14: dffffc0000000000 R15: ffff8880a6b2ec10
tracepoint_probe_register_prio kernel/tracepoint.c:315 [inline]
tracepoint_probe_register+0x9c/0xe0 kernel/tracepoint.c:335
__bpf_probe_register kernel/trace/bpf_trace.c:1950 [inline]
bpf_probe_register+0x16c/0x1d0 kernel/trace/bpf_trace.c:1955
bpf_raw_tracepoint_open+0x34e/0xb20 kernel/bpf/syscall.c:2741
__do_sys_bpf+0x1b2f/0x4c60 kernel/bpf/syscall.c:4220
do_syscall_64+0x2d/0x70 arch/x86/entry/common.c:46
entry_SYSCALL_64_after_hwframe+0x44/0xa9
RIP: 0033:0x4415a9
Code: e8 ac e8 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 8b 09 fc ff c3 66 2e 0f 1f 84 00 00 00 00
RSP: 002b:00007ffc28dd5d08 EFLAGS: 00000246 ORIG_RAX: 0000000000000141
RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00000000004415a9
RDX: 0000000000000010 RSI: 0000000020000040 RDI: 0000000000000011
RBP: 0000000000010308 R08: 00000000004002c8 R09: 00000000004002c8
R10: 0000000000000004 R11: 0000000000000246 R12: 00000000004023c0
R13: 0000000000402450 R14: 0000000000000000 R15: 0000000000000000

sachin Gupta

unread,
Oct 2, 2022, 4:04:27 AM10/2/22
to syzkaller-bugs
Hi I've implemented a trace hooks and after implementing its giving warnings
. Can anybody help me with bypassing those warnings.

Dmitry Vyukov

unread,
Oct 4, 2022, 2:52:07 AM10/4/22
to sachin Gupta, syzkaller-bugs
On Sun, 2 Oct 2022 at 10:04, sachin Gupta <iiita.sa...@gmail.com> wrote:
>
> Hi I've implemented a trace hooks and after implementing its giving warnings
> . Can anybody help me with bypassing those warnings.

Hi sachin,

If you are looking for help from kernel developers, you need to
contact relevant kernel mailing lists. There are no kernel devs on
syzkaller-bugs@ mailing list.
> --
> You received this message because you are subscribed to the Google Groups "syzkaller-bugs" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to syzkaller-bug...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/syzkaller-bugs/679bf9b9-bea0-4cf2-a5b8-422582e8ea5cn%40googlegroups.com.
Reply all
Reply to author
Forward
0 new messages