WARNING in perf_trace_buf_alloc

6 views
Skip to first unread message

syzbot

unread,
Oct 27, 2017, 3:24:04 AM10/27/17
to syzkaller-upst...@googlegroups.com
Hello,

syzkaller hit the following crash on
31fc38c476237a405651de3faf5d3e5984c46f12
git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/master
compiler: gcc (GCC) 7.1.1 20170620
.config is attached
Raw console output is attached.
C reproducer is attached
syzkaller reproducer is attached. See https://goo.gl/kgGztJ
for information about syzkaller reproducers
CC: [linux-...@vger.kernel.org mi...@redhat.com ros...@goodmis.org]

------------[ cut here ]------------
WARNING: CPU: 0 PID: 3005 at kernel/trace/trace_event_perf.c:274
perf_trace_buf_alloc+0x12d/0x160 kernel/trace/trace_event_perf.c:273
Kernel panic - not syncing: panic_on_warn set ...

CPU: 0 PID: 3005 Comm: syzkaller361563 Not tainted 4.13.0-next-20170914+ #4
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Bochs 01/01/2011
Call Trace:
__dump_stack lib/dump_stack.c:16 [inline]
dump_stack+0x194/0x257 lib/dump_stack.c:52
panic+0x1e4/0x417 kernel/panic.c:181
__warn+0x1c4/0x1d9 kernel/panic.c:542
report_bug+0x211/0x2d0 lib/bug.c:183
fixup_bug+0x40/0x90 arch/x86/kernel/traps.c:178
do_trap_no_signal arch/x86/kernel/traps.c:212 [inline]
do_trap+0x260/0x390 arch/x86/kernel/traps.c:261
do_error_trap+0x120/0x390 arch/x86/kernel/traps.c:298
do_invalid_op+0x1b/0x20 arch/x86/kernel/traps.c:311
invalid_op+0x18/0x20 arch/x86/entry/entry_64.S:905
RIP: 0010:perf_trace_buf_alloc+0x12d/0x160
kernel/trace/trace_event_perf.c:273
RSP: 0018:ffff88006ca67760 EFLAGS: 00010286
RAX: 000000000000001c RBX: 1ffff1000d94cefe RCX: 0000000000000000
RDX: 000000000000001c RSI: 1ffff1000d94ceac RDI: ffffed000d94cee0
RBP: ffff88006ca67780 R08: ffff88006ca66e50 R09: 0000000000000000
R10: ffff88006ba5c440 R11: 0000000000000000 R12: 0000000000000e54
R13: ffff88006ca67810 R14: ffff88006ca67890 R15: ffff88003d9bccc0
perf_trace_bpf_map_keyval+0x260/0xbd0 include/trace/events/bpf.h:227
trace_bpf_map_update_elem include/trace/events/bpf.h:273 [inline]
map_update_elem kernel/bpf/syscall.c:595 [inline]
SYSC_bpf kernel/bpf/syscall.c:1476 [inline]
SyS_bpf+0x33f4/0x46a0 kernel/bpf/syscall.c:1451
entry_SYSCALL_64_fastpath+0x1f/0xbe
RIP: 0033:0x434fe9
RSP: 002b:00007ffcb22cada8 EFLAGS: 00000207 ORIG_RAX: 0000000000000141
RAX: ffffffffffffffda RBX: ffffffffffffffff RCX: 0000000000434fe9
RDX: 0000000000000020 RSI: 000000002000b000 RDI: 0000000000000002
RBP: 0000000000000082 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000207 R12: 0000000000000000
R13: 0000000000401960 R14: 00000000004019f0 R15: 0000000000000000
Dumping ftrace buffer:
(ftrace buffer empty)
Kernel Offset: disabled
Rebooting in 86400 seconds..


---
This bug is generated by a dumb bot. It may contain errors.
See https://goo.gl/tpsmEJ for details.
Direct all questions to syzk...@googlegroups.com.

syzbot will keep track of this bug report.
Once a fix for this bug is committed, please reply to this email with:
#syz fix: exact-commit-title
To mark this as a duplicate of another syzbot report, please reply with:
#syz dup: exact-subject-of-another-report
If it's a one-off invalid bug report, please reply with:
#syz invalid
Note: if the crash happens again, it will cause creation of a new bug
report.
To upstream this report, please reply with:
#syz upstream
config.txt
raw.log
repro.txt
repro.c

Dmitry Vyukov

unread,
Oct 27, 2017, 4:14:04 AM10/27/17
to syzbot, 'Dmitry Vyukov' via syzkaller-upstream-moderation
This does not reproduce anymore (tried on
15f859ae5c43c7f0a064ed92d33f7a5bc5de6de0)
#syz invalid

On Fri, Oct 27, 2017 at 9:24 AM, syzbot
<bot+f33ed74fc97df9dd4f...@syzkaller.appspotmail.com>
wrote:
> --
> You received this message because you are subscribed to the Google Groups
> "syzkaller-upstream-moderation" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to syzkaller-upstream-m...@googlegroups.com.
> To post to this group, send email to
> syzkaller-upst...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/syzkaller-upstream-moderation/001a113fdbf64ea732055c822cf8%40google.com.
> For more options, visit https://groups.google.com/d/optout.
Reply all
Reply to author
Forward
0 new messages