All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+10189b9b0f8c4664badd@syzkaller.appspotmail.com>
To: acme@kernel.org, acme@redhat.com,
	alexander.shishkin@linux.intel.com, bp@alien8.de,
	eranian@google.com, hpa@zytor.com, jolsa@kernel.org,
	jolsa@redhat.com, kan.liang@linux.intel.com,
	linux-kernel@vger.kernel.org, mingo@kernel.org, mingo@redhat.com,
	peterz@infradead.org, syzkaller-bugs@googlegroups.com,
	tglx@linutronix.de, torvalds@linux-foundation.org,
	vincent.weaver@maine.edu, x86@kernel.org
Subject: WARNING in perf_reg_value
Date: Wed, 19 Jun 2019 12:47:05 -0700	[thread overview]
Message-ID: <000000000000734545058bb27ebb@google.com> (raw)

Hello,

syzbot found the following crash on:

HEAD commit:    0011572c Merge branch 'for-5.2-fixes' of git://git.kernel...
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=12c38d66a00000
kernel config:  https://syzkaller.appspot.com/x/.config?x=fa9f7e1b6a8bb586
dashboard link: https://syzkaller.appspot.com/bug?extid=10189b9b0f8c4664badd
compiler:       gcc (GCC) 9.0.0 20181231 (experimental)
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=1434b876a00000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=10e6c876a00000

The bug was bisected to:

commit 878068ea270ea82767ff1d26c91583263c81fba0
Author: Kan Liang <kan.liang@linux.intel.com>
Date:   Tue Apr 2 19:44:59 2019 +0000

     perf/x86: Support outputting XMM registers

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=14556d66a00000
final crash:    https://syzkaller.appspot.com/x/report.txt?x=16556d66a00000
console output: https://syzkaller.appspot.com/x/log.txt?x=12556d66a00000

IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+10189b9b0f8c4664badd@syzkaller.appspotmail.com
Fixes: 878068ea270e ("perf/x86: Support outputting XMM registers")

WARNING: CPU: 0 PID: 8516 at arch/x86/kernel/perf_regs.c:71  
perf_reg_value+0xdb/0x110 arch/x86/kernel/perf_regs.c:75
Kernel panic - not syncing: panic_on_warn set ...
CPU: 0 PID: 8516 Comm: syz-executor483 Not tainted 5.2.0-rc4+ #32
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+0x2cb/0x744 kernel/panic.c:219
  __warn.cold+0x20/0x4d kernel/panic.c:576
  report_bug+0x263/0x2b0 lib/bug.c:186
  fixup_bug arch/x86/kernel/traps.c:179 [inline]
  fixup_bug arch/x86/kernel/traps.c:174 [inline]
  do_error_trap+0x11b/0x200 arch/x86/kernel/traps.c:272
  do_invalid_op+0x37/0x50 arch/x86/kernel/traps.c:291
  invalid_op+0x14/0x20 arch/x86/entry/entry_64.S:986
RIP: 0010:perf_reg_value+0xdb/0x110 arch/x86/kernel/perf_regs.c:71
Code: a0 00 00 00 77 26 48 b8 00 00 00 00 00 fc ff df 48 01 fb 48 89 da 48  
c1 ea 03 80 3c 02 00 75 34 48 8b 03 48 83 c4 08 5b 5d c3 <0f> 0b 48 83 c4  
08 31 c0 5b 5d c3 89 75 f0 e8 72 d6 78 00 8b 75 f0
RSP: 0018:ffff88809674f2b8 EFLAGS: 00010202
RAX: 00000000fffffff9 RBX: ffff88809674fa68 RCX: ffffffff81855a4e
RDX: 0000000000000000 RSI: 0000000000000019 RDI: ffff88809674fa68
RBP: ffff88809674f2c8 R08: ffff888092eda5c0 R09: ffffed1012f92ebb
R10: ffffed1012f92eba R11: ffff888097c975d7 R12: ffff88809674f320
R13: ffff88809674f508 R14: ffff88809674fa68 R15: ffff88809674f700
  perf_output_sample_regs+0xca/0x160 kernel/events/core.c:5914
  perf_output_sample+0x15c2/0x1a90 kernel/events/core.c:6351
  __perf_event_output kernel/events/core.c:6571 [inline]
  perf_event_output_forward+0x150/0x290 kernel/events/core.c:6585
  __perf_event_overflow+0x141/0x370 kernel/events/core.c:8052
  perf_swevent_overflow+0xaa/0x140 kernel/events/core.c:8128
  perf_swevent_event+0x1f7/0x2f0 kernel/events/core.c:8161
  do_perf_sw_event kernel/events/core.c:8269 [inline]
  ___perf_sw_event+0x31c/0x570 kernel/events/core.c:8300
  __perf_sw_event+0x51/0xa0 kernel/events/core.c:8312
  perf_sw_event include/linux/perf_event.h:1083 [inline]
  do_user_addr_fault arch/x86/mm/fault.c:1498 [inline]
  __do_page_fault+0x747/0xda0 arch/x86/mm/fault.c:1523
  do_page_fault+0x71/0x57d arch/x86/mm/fault.c:1554
  page_fault+0x1e/0x30 arch/x86/entry/entry_64.S:1156
RIP: 0010:copy_user_enhanced_fast_string+0xe/0x20  
arch/x86/lib/copy_user_64.S:205
Code: 89 d1 c1 e9 03 83 e2 07 f3 48 a5 89 d1 f3 a4 31 c0 0f 1f 00 c3 0f 1f  
80 00 00 00 00 0f 1f 00 83 fa 40 0f 82 70 ff ff ff 89 d1 <f3> a4 31 c0 0f  
1f 00 c3 66 2e 0f 1f 84 00 00 00 00 00 89 d1 f3 a4
RSP: 0018:ffff88809674fb10 EFLAGS: 00010206
RAX: 0000000000000000 RBX: 0000000000001000 RCX: 00000000000001c0
RDX: 0000000000001000 RSI: 0000000020001000 RDI: ffff888099b30e40
RBP: ffff88809674fb48 R08: ffffed1013366200 R09: 0000000000000000
R10: ffffed10133661ff R11: ffff888099b30fff R12: 00000000200001c0
R13: ffff888099b30000 R14: 00000000200011c0 R15: 00007ffffffff000
  copy_page_from_iter_iovec lib/iov_iter.c:295 [inline]
  copy_page_from_iter+0x3ad/0x7d0 lib/iov_iter.c:921
  pipe_write+0x281/0xf30 fs/pipe.c:454
  call_write_iter include/linux/fs.h:1872 [inline]
  new_sync_write+0x4d3/0x770 fs/read_write.c:483
  __vfs_write+0xe1/0x110 fs/read_write.c:496
  vfs_write+0x20c/0x580 fs/read_write.c:558
  ksys_write+0x14f/0x290 fs/read_write.c:611
  __do_sys_write fs/read_write.c:623 [inline]
  __se_sys_write fs/read_write.c:620 [inline]
  __x64_sys_write+0x73/0xb0 fs/read_write.c:620
  do_syscall_64+0xfd/0x680 arch/x86/entry/common.c:301
  entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x440529
Code: 18 89 d0 c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 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 fb 13 fc ff c3 66 2e 0f 1f 84 00 00 00 00
RSP: 002b:00007ffe36867c38 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 00000000004002c8 RCX: 0000000000440529
RDX: 000000010000026f RSI: 00000000200001c0 RDI: 0000000000000007
RBP: 00000000006ca018 R08: 0000000000000000 R09: 00000000004002c8
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000401db0
R13: 0000000000401e40 R14: 0000000000000000 R15: 0000000000000000
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 syzkaller@googlegroups.com.

syzbot will keep track of this bug report. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
syzbot can test patches for this bug, for details see:
https://goo.gl/tpsmEJ#testing-patches

             reply	other threads:[~2019-06-19 19:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-19 19:47 syzbot [this message]
2019-06-19 20:07 ` WARNING in perf_reg_value Vince Weaver
2019-06-19 21:15   ` Liang, Kan
2019-06-20 12:13     ` Peter Zijlstra
2019-12-08  5:03 ` syzbot

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=000000000000734545058bb27ebb@google.com \
    --to=syzbot+10189b9b0f8c4664badd@syzkaller.appspotmail.com \
    --cc=acme@kernel.org \
    --cc=acme@redhat.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=bp@alien8.de \
    --cc=eranian@google.com \
    --cc=hpa@zytor.com \
    --cc=jolsa@kernel.org \
    --cc=jolsa@redhat.com \
    --cc=kan.liang@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.org \
    --cc=vincent.weaver@maine.edu \
    --cc=x86@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.