From: Mike Galbraith <umgwanakikbuti@gmail.com>
To: Jeff Merkey <linux.mdb@gmail.com>, linux-kernel@vger.kernel.org
Cc: tglx@linutronix.de, mingo@redhat.com, hpa@zytor.com,
x86@kernel.org, peterz@infradead.org, luto@kernel.org
Subject: Re: [PATCH v4] Fix INT1 Recursion with unregistered breakpoints
Date: Sun, 20 Dec 2015 03:31:51 +0100 [thread overview]
Message-ID: <1450578711.3793.8.camel@gmail.com> (raw)
In-Reply-To: <20151220021347.GA14466@localhost.localdomain>
On Sat, 2015-12-19 at 19:13 -0700, Jeff Merkey wrote:
> @@ -519,6 +528,18 @@ static int hw_breakpoint_handler(struct die_args
> *args)
> (dr6 & (~DR_TRAP_BITS)))
> rc = NOTIFY_DONE;
>
> + /*
> + * if we are about to signal to
> + * do_debug() to stop further processing
> + * and we have not ascertained the source
> + * of the breakpoint, log it as spurious.
> + */
Ahem...
next prev parent reply other threads:[~2015-12-20 2:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-20 2:13 [PATCH v4] Fix INT1 Recursion with unregistered breakpoints Jeff Merkey
2015-12-20 2:31 ` Mike Galbraith [this message]
2015-12-20 2:34 ` Jeff Merkey
2015-12-20 2:36 ` Jeff Merkey
2015-12-20 2:39 ` 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=1450578711.3793.8.camel@gmail.com \
--to=umgwanakikbuti@gmail.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux.mdb@gmail.com \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.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 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.