From: syzbot <syzbot+370a6b0f11867bf13515@syzkaller.appspotmail.com>
To: bp@alien8.de, frederic@kernel.org, gustavo@embeddedor.com,
hpa@zytor.com, linux-kernel@vger.kernel.org, mhiramat@kernel.org,
mingo@redhat.com, syzkaller-bugs@googlegroups.com,
tglx@linutronix.de, x86@kernel.org
Subject: Re: WARNING in arch_install_hw_breakpoint
Date: Sun, 24 Mar 2019 02:23:04 -0700 [thread overview]
Message-ID: <000000000000a0482e0584d3a24a@google.com> (raw)
In-Reply-To: <000000000000639f6a0584d11b82@google.com>
syzbot has found a reproducer for the following crash on:
HEAD commit: fd1f297b Merge tag 'drm-fixes-2019-03-22' of git://anongit..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1574f56d200000
kernel config: https://syzkaller.appspot.com/x/.config?x=9a31fb246de2a622
dashboard link: https://syzkaller.appspot.com/bug?extid=370a6b0f11867bf13515
compiler: gcc (GCC) 9.0.0 20181231 (experimental)
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1157b7cf200000
Bisection is inconclusive: the bug happens on the oldest tested release.
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=10ca39b3200000
final crash: https://syzkaller.appspot.com/x/report.txt?x=12ca39b3200000
console output: https://syzkaller.appspot.com/x/log.txt?x=14ca39b3200000
IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+370a6b0f11867bf13515@syzkaller.appspotmail.com
------------[ cut here ]------------
Can't find any breakpoint slot
WARNING: CPU: 0 PID: 8058 at arch/x86/kernel/hw_breakpoint.c:121
arch_install_hw_breakpoint+0x2d6/0x3a0 arch/x86/kernel/hw_breakpoint.c:121
Kernel panic - not syncing: panic_on_warn set ...
CPU: 0 PID: 8058 Comm: syz-executor.1 Not tainted 5.1.0-rc1+ #33
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/0x65c kernel/panic.c:214
__warn.cold+0x20/0x45 kernel/panic.c:571
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:973
RIP: 0010:arch_install_hw_breakpoint+0x2d6/0x3a0
arch/x86/kernel/hw_breakpoint.c:121
Code: c8 48 83 c4 18 5b 41 5c 41 5d 41 5e 41 5f 5d c3 0f 0b 0f 0b 48 c7 c7
40 23 65 87 89 45 d4 c6 05 ed 9d 32 08 01 e8 98 43 1b 00 <0f> 0b 8b 45 d4
e9 bc fd ff ff 40 88 75 c8 e8 a7 8e 80 00 0f b6 75
RSP: 0018:ffff8880a512f6d8 EFLAGS: 00010086
RAX: 0000000000000000 RBX: ffff8880ae81ec98 RCX: 0000000000000000
RDX: 0000000040000000 RSI: ffffffff815ae266 RDI: ffffed1014a25ecd
RBP: ffff8880a512f718 R08: ffff8880857382c0 R09: fffffbfff11335f5
R10: fffffbfff11335f4 R11: ffffffff8899afa3 R12: ffff888085730380
R13: dffffc0000000000 R14: 0000000000000004 R15: 000000000001eca0
hw_breakpoint_add+0xa7/0x130 kernel/events/hw_breakpoint.c:632
event_sched_in kernel/events/core.c:2281 [inline]
event_sched_in.isra.0+0x373/0xbf0 kernel/events/core.c:2245
group_sched_in+0xe4/0x3d0 kernel/events/core.c:2317
flexible_sched_in+0x615/0x9c0 kernel/events/core.c:3311
visit_groups_merge+0x336/0x5d0 kernel/events/core.c:3259
ctx_flexible_sched_in kernel/events/core.c:3345 [inline]
ctx_sched_in+0x330/0x670 kernel/events/core.c:3390
perf_event_sched_in+0x6e/0xa0 kernel/events/core.c:2426
perf_event_context_sched_in kernel/events/core.c:3430 [inline]
__perf_event_task_sched_in+0x609/0x820 kernel/events/core.c:3469
perf_event_task_sched_in include/linux/perf_event.h:1115 [inline]
finish_task_switch+0x2c2/0x780 kernel/sched/core.c:2725
context_switch kernel/sched/core.c:2880 [inline]
__schedule+0x81f/0x1cc0 kernel/sched/core.c:3518
schedule+0x92/0x180 kernel/sched/core.c:3562
freezable_schedule include/linux/freezer.h:172 [inline]
ptrace_stop+0x3fe/0x950 kernel/signal.c:2111
do_jobctl_trap kernel/signal.c:2330 [inline]
get_signal+0x1502/0x1d50 kernel/signal.c:2456
do_signal+0x87/0x1940 arch/x86/kernel/signal.c:816
exit_to_usermode_loop+0x244/0x2c0 arch/x86/entry/common.c:162
prepare_exit_to_usermode arch/x86/entry/common.c:197 [inline]
syscall_return_slowpath arch/x86/entry/common.c:268 [inline]
do_syscall_64+0x52d/0x610 arch/x86/entry/common.c:293
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x458209
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:00007f6b1a2a8c78 EFLAGS: 00000246 ORIG_RAX: 0000000000000129
RAX: 0000000000000000 RBX: 0000000000000004 RCX: 0000000000458209
RDX: 0000000000000016 RSI: 000000000000002a RDI: 000000000000002a
RBP: 000000000073bf00 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000020000100 R11: 0000000000000246 R12: 00007f6b1a2a96d4
R13: 00000000004c4f84 R14: 00000000004d8bd8 R15: 00000000ffffffff
======================================================
next prev parent reply other threads:[~2019-03-24 9:23 UTC|newest]
Thread overview: 233+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-24 6:22 WARNING in arch_install_hw_breakpoint syzbot
2019-03-24 6:23 ` syzbot
2019-03-24 6:24 ` syzbot
2019-03-24 6:25 ` syzbot
2019-03-24 6:26 ` syzbot
2019-03-24 6:27 ` syzbot
2019-03-24 6:28 ` syzbot
2019-03-24 6:29 ` syzbot
2019-03-24 6:30 ` syzbot
2019-03-24 6:31 ` syzbot
2019-03-24 6:32 ` syzbot
2019-03-24 6:33 ` syzbot
2019-03-24 6:34 ` syzbot
2019-03-24 6:35 ` syzbot
2019-03-24 6:36 ` syzbot
2019-03-24 6:37 ` syzbot
2019-03-24 6:38 ` syzbot
2019-03-24 6:39 ` syzbot
2019-03-24 6:40 ` syzbot
2019-03-24 6:41 ` syzbot
2019-03-24 6:42 ` syzbot
2019-03-24 6:43 ` syzbot
2019-03-24 6:44 ` syzbot
2019-03-24 6:45 ` syzbot
2019-03-24 6:46 ` syzbot
2019-03-24 6:47 ` syzbot
2019-03-24 6:48 ` syzbot
2019-03-24 6:49 ` syzbot
2019-03-24 6:50 ` syzbot
2019-03-24 6:51 ` syzbot
2019-03-24 6:52 ` syzbot
2019-03-24 6:53 ` syzbot
2019-03-24 6:54 ` syzbot
2019-03-24 6:55 ` syzbot
2019-03-24 6:56 ` syzbot
2019-03-24 6:57 ` syzbot
2019-03-24 6:58 ` syzbot
2019-03-24 6:59 ` syzbot
2019-03-24 7:00 ` syzbot
2019-03-24 7:01 ` syzbot
2019-03-24 7:02 ` syzbot
2019-03-24 7:03 ` syzbot
2019-03-24 7:04 ` syzbot
2019-03-24 7:05 ` syzbot
2019-03-24 7:06 ` syzbot
2019-03-24 7:07 ` syzbot
2019-03-24 7:08 ` syzbot
2019-03-24 7:09 ` syzbot
2019-03-24 7:10 ` syzbot
2019-03-24 7:11 ` syzbot
2019-03-24 7:12 ` syzbot
2019-03-24 7:13 ` syzbot
2019-03-24 7:14 ` syzbot
2019-03-24 7:15 ` syzbot
2019-03-24 7:16 ` syzbot
2019-03-24 7:17 ` syzbot
2019-03-24 7:18 ` syzbot
2019-03-24 7:19 ` syzbot
2019-03-24 7:20 ` syzbot
2019-03-24 7:21 ` syzbot
2019-03-24 7:22 ` syzbot
2019-03-24 7:23 ` syzbot
2019-03-24 7:24 ` syzbot
2019-03-24 7:25 ` syzbot
2019-03-24 7:26 ` syzbot
2019-03-24 7:27 ` syzbot
2019-03-24 7:28 ` syzbot
2019-03-24 7:29 ` syzbot
2019-03-24 7:30 ` syzbot
2019-03-24 7:31 ` syzbot
2019-03-24 7:32 ` syzbot
2019-03-24 7:33 ` syzbot
2019-03-24 7:34 ` syzbot
2019-03-24 7:35 ` syzbot
2019-03-24 7:36 ` syzbot
2019-03-24 7:37 ` syzbot
2019-03-24 7:38 ` syzbot
2019-03-24 7:39 ` syzbot
2019-03-24 7:40 ` syzbot
2019-03-24 7:41 ` syzbot
2019-03-24 7:42 ` syzbot
2019-03-24 7:43 ` syzbot
2019-03-24 7:44 ` syzbot
2019-03-24 7:45 ` syzbot
2019-03-24 7:46 ` syzbot
2019-03-24 7:47 ` syzbot
2019-03-24 7:48 ` syzbot
2019-03-24 7:49 ` syzbot
2019-03-24 7:50 ` syzbot
2019-03-24 7:51 ` syzbot
2019-03-24 7:52 ` syzbot
2019-03-24 7:53 ` syzbot
2019-03-24 7:54 ` syzbot
2019-03-24 7:55 ` syzbot
2019-03-24 7:56 ` syzbot
2019-03-24 7:57 ` syzbot
2019-03-24 7:58 ` syzbot
2019-03-24 7:59 ` syzbot
2019-03-24 8:00 ` syzbot
2019-03-24 8:01 ` syzbot
2019-03-24 8:02 ` syzbot
2019-03-24 8:03 ` syzbot
2019-03-24 8:04 ` syzbot
2019-03-24 8:05 ` syzbot
2019-03-24 8:06 ` syzbot
2019-03-24 8:07 ` syzbot
2019-03-24 8:08 ` syzbot
2019-03-24 8:09 ` syzbot
2019-03-24 8:10 ` syzbot
2019-03-24 8:11 ` syzbot
2019-03-24 8:12 ` syzbot
2019-03-24 8:13 ` syzbot
2019-03-24 8:14 ` syzbot
2019-03-24 8:15 ` syzbot
2019-03-24 8:16 ` syzbot
2019-03-24 8:17 ` syzbot
2019-03-24 8:18 ` syzbot
2019-03-24 8:19 ` syzbot
2019-03-24 8:20 ` syzbot
2019-03-24 8:21 ` syzbot
2019-03-24 8:22 ` syzbot
2019-03-24 8:23 ` syzbot
2019-03-24 8:24 ` syzbot
2019-03-24 8:25 ` syzbot
2019-03-24 8:26 ` syzbot
2019-03-24 8:27 ` syzbot
2019-03-24 8:28 ` syzbot
2019-03-24 8:29 ` syzbot
2019-03-24 8:30 ` syzbot
2019-03-24 8:31 ` syzbot
2019-03-24 8:32 ` syzbot
2019-03-24 8:33 ` syzbot
2019-03-24 8:34 ` syzbot
2019-03-24 8:35 ` syzbot
2019-03-24 8:36 ` syzbot
2019-03-24 8:37 ` syzbot
2019-03-24 8:38 ` syzbot
2019-03-24 8:39 ` syzbot
2019-03-24 8:40 ` syzbot
2019-03-24 8:41 ` syzbot
2019-03-24 8:42 ` syzbot
2019-03-24 8:43 ` syzbot
2019-03-24 8:44 ` syzbot
2019-03-24 8:45 ` syzbot
2019-03-24 8:46 ` syzbot
2019-03-24 8:47 ` syzbot
2019-03-24 8:48 ` syzbot
2019-03-24 8:49 ` syzbot
2019-03-24 8:50 ` syzbot
2019-03-24 8:51 ` syzbot
2019-03-24 8:52 ` syzbot
2019-03-24 8:53 ` syzbot
2019-03-24 8:54 ` syzbot
2019-03-24 8:55 ` syzbot
2019-03-24 8:56 ` syzbot
2019-03-24 8:57 ` syzbot
2019-03-24 8:58 ` syzbot
2019-03-24 8:59 ` syzbot
2019-03-24 9:00 ` syzbot
2019-03-24 9:01 ` syzbot
2019-03-24 9:02 ` syzbot
2019-03-24 9:03 ` syzbot
2019-03-24 9:04 ` syzbot
2019-03-24 9:05 ` syzbot
2019-03-24 9:06 ` syzbot
2019-03-24 9:07 ` syzbot
2019-03-24 9:07 ` Borislav Petkov
2019-03-24 13:07 ` Dmitry Vyukov
2019-03-24 14:00 ` Borislav Petkov
2019-03-24 9:08 ` syzbot
2019-03-24 9:09 ` syzbot
2019-03-24 9:10 ` syzbot
2019-03-24 9:11 ` syzbot
2019-03-24 9:12 ` syzbot
2019-03-24 9:13 ` syzbot
2019-03-24 9:14 ` syzbot
2019-03-24 9:15 ` syzbot
2019-03-24 9:16 ` syzbot
2019-03-24 9:17 ` syzbot
2019-03-24 9:18 ` syzbot
2019-03-24 9:19 ` syzbot
2019-03-24 9:20 ` syzbot
2019-03-24 9:21 ` syzbot
2019-03-24 9:22 ` syzbot
2019-03-24 9:23 ` syzbot [this message]
2019-03-24 9:24 ` syzbot
2019-03-24 9:25 ` syzbot
2019-03-24 9:26 ` syzbot
2019-03-24 9:27 ` syzbot
2019-03-24 9:28 ` syzbot
2019-03-24 9:29 ` syzbot
2019-03-24 9:30 ` syzbot
2019-03-24 9:31 ` syzbot
2019-03-24 9:32 ` syzbot
2019-03-24 9:33 ` syzbot
2019-03-24 9:34 ` syzbot
2019-03-24 9:35 ` syzbot
2019-03-24 9:36 ` syzbot
2019-03-24 9:37 ` syzbot
2019-03-24 9:38 ` syzbot
2019-03-24 9:39 ` syzbot
2019-03-24 9:40 ` syzbot
2019-03-24 9:41 ` syzbot
2019-03-24 9:42 ` syzbot
2019-03-24 9:43 ` syzbot
2019-03-24 9:44 ` syzbot
2019-03-24 9:45 ` syzbot
2019-03-24 9:46 ` syzbot
2019-03-24 9:47 ` syzbot
2019-03-24 9:48 ` syzbot
2019-03-24 9:49 ` syzbot
2019-03-24 9:50 ` syzbot
2019-03-24 9:51 ` syzbot
2019-03-24 9:52 ` syzbot
2019-03-24 9:53 ` syzbot
2019-03-24 9:54 ` syzbot
2019-03-24 9:55 ` syzbot
2019-03-24 9:56 ` syzbot
2019-03-24 9:57 ` syzbot
2019-03-24 9:58 ` syzbot
2019-03-24 9:59 ` syzbot
2019-03-24 10:00 ` syzbot
2019-03-24 10:01 ` syzbot
2019-03-24 10:02 ` syzbot
2019-03-24 10:03 ` syzbot
2019-03-27 13:28 ` Borislav Petkov
2019-03-27 13:45 ` Dmitry Vyukov
2019-03-27 15:17 ` Borislav Petkov
2019-03-27 17:48 ` Borislav Petkov
2019-03-28 5:27 ` Frederic Weisbecker
2019-12-08 15:33 ` syzbot
2019-12-10 0:10 ` Kees Cook
2019-12-10 9:23 ` Christian Brauner
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=000000000000a0482e0584d3a24a@google.com \
--to=syzbot+370a6b0f11867bf13515@syzkaller.appspotmail.com \
--cc=bp@alien8.de \
--cc=frederic@kernel.org \
--cc=gustavo@embeddedor.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=mingo@redhat.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).