From: Ingo Molnar <mingo@kernel.org>
To: Jeff Merkey <linux.mdb@gmail.com>
Cc: Andy Lutomirski <luto@amacapital.net>,
Thomas Gleixner <tglx@linutronix.de>,
LKML <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
X86 ML <x86@kernel.org>, Peter Zijlstra <peterz@infradead.org>,
Andy Lutomirski <luto@kernel.org>,
Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>,
Steven Rostedt <rostedt@goodmis.org>,
Borislav Petkov <bp@alien8.de>, Jiri Olsa <jolsa@kernel.org>
Subject: Re: [PATCH 1/1] Fix int1 recursion when no perf_bp_event is registeredy
Date: Mon, 14 Dec 2015 09:09:14 +0100 [thread overview]
Message-ID: <20151214080914.GA20556@gmail.com> (raw)
In-Reply-To: <CAO6TR8WwF9XDvGykyZX+qT8LDJEi-QN7t-LTPF0N_qPVeM1Puw@mail.gmail.com>
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
* Jeff Merkey <linux.mdb@gmail.com> wrote:
> I trigger it by writing to the dr7 and dr1, 2, 3 or four register and
> set an execute breakpoint without going through
> arch_install_hw_breakpoint. When the breakpoint fires, the system
> crashes and hangs on the processor stuck in an endless loop inside the
> int1 handler in hw_breakpoint.c --
What is still not clear to me, can you trigger the hang not via some special
kernel driver that goes outside regular APIs and messes with the state of the
debug registers, but via the proper access methods, i.e. various user-space ABIs?
Thanks,
Ingo
next prev parent reply other threads:[~2015-12-14 8:09 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-10 7:12 [PATCH 1/1] Fix int1 recursion when no perf_bp_event is registered Jeff Merkey
2015-12-10 18:55 ` Thomas Gleixner
2015-12-10 19:09 ` Andy Lutomirski
2015-12-10 19:20 ` Jiri Olsa
2015-12-10 19:25 ` Borislav Petkov
2015-12-10 20:49 ` [PATCH 1/1] Fix int1 recursion when no perf_bp_event is registeredy Thomas Gleixner
2015-12-10 21:09 ` Andy Lutomirski
2015-12-10 21:15 ` Thomas Gleixner
2015-12-10 21:26 ` Jeff Merkey
2015-12-10 21:16 ` Jeff Merkey
2015-12-14 8:09 ` Ingo Molnar [this message]
2015-12-14 8:13 ` Jeff Merkey
2015-12-14 8:26 ` Jeff Merkey
2015-12-14 9:28 ` Ingo Molnar
2015-12-14 17:52 ` Jeff Merkey
2015-12-14 17:56 ` Andy Lutomirski
2015-12-14 18:16 ` Jeff Merkey
2015-12-14 18:18 ` Jeff Merkey
2015-12-10 21:11 ` Jeff Merkey
2015-12-10 22:26 ` Jeff Merkey
2015-12-11 8:05 ` [PATCH v2 " Jeff Merkey
2015-12-11 19:04 ` Jeff Merkey
2015-12-13 23:11 ` Jeff Merkey
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=20151214080914.GA20556@gmail.com \
--to=mingo@kernel.org \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux.mdb@gmail.com \
--cc=luto@amacapital.net \
--cc=luto@kernel.org \
--cc=masami.hiramatsu.pt@hitachi.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--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