linux-kernel - Re: [PATCH v2] Fix INT1 Exception with unregistered breakpoints

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CAO6TR8UGCs6cuV6GtxAfPA1cX_xt-RgosqqNqWt6dd6TX9J_Vg@mail.gmail.com>
Date:	Mon, 14 Dec 2015 21:52:27 -0700
From:	Jeff Merkey <linux.mdb@...il.com>
To:	"H. Peter Anvin" <hpa@...or.com>
Cc:	linux-kernel@...r.kernel.org, tglx@...utronix.de, mingo@...hat.com,
	x86@...nel.org, peterz@...radead.org, luto@...nel.org
Subject: Re: [PATCH v2] Fix INT1 Exception with unregistered breakpoints

On 12/14/15, H. Peter Anvin <hpa@...or.com> wrote:
> On December 14, 2015 4:49:51 PM PST, Jeff Merkey <linux.mdb@...il.com>
> wrote:
>>On 12/14/15, Jeff Merkey <linux.mdb@...il.com> wrote:
>>> Please consider the attached patch.
>>>
>>> SUMMARY
>>>
>>> This patch corrects a hard lockup failure of the system kernel if the
>>> operating system receives a breakpoint exception at a code execution
>>> address which was not registered with the operating system.  The
>>patch
>>> allows kernel debuggers, application profiling and performance
>>modules,
>>> and external debugging tools to work better together at sharing the
>>> breakpoint registers on the platform in a way that they do not cause
>>> errors and system faults, and enables the full feature set in the
>>> breakpoint API.  If a kernel application triggers a breakpoint
>>> or programs one in error, this patch will catch the condition and
>>report
>>> it to the system log without the operating system experiencing a
>>system
>>> fault.  There are several consumers of the Linux Breakpoint API and
>>all
>>> of them can and sometimes do cause the condition this patch corrects.
>>>
>>
>>Peter,
>>
>>Is that the type of summary that meets the standards.  I tried to be
>>concise.
>>
>>Jeff
>
> It would be good if you could be a bit more precise.  In particular, explain
> how and why the condition can appear rather than just explain that it can.
> --
> Sent from my Android device with K-9 Mail. Please excuse brevity and
> formatting.
>

Yes sir.  I'll be more concise and re-submit

Jeff
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/