linux-kernel - Re: [PATCH v4] Fix INT1 Recursion 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] [thread-next>] [day] [month] [year] [list]

Date:	Sat, 19 Dec 2015 19:36:35 -0700
From:	Jeff Merkey <linux.mdb@...il.com>
To:	Mike Galbraith <umgwanakikbuti@...il.com>
Cc:	linux-kernel@...r.kernel.org, tglx@...utronix.de, mingo@...hat.com,
	hpa@...or.com, x86@...nel.org, peterz@...radead.org,
	luto@...nel.org
Subject: Re: [PATCH v4] Fix INT1 Recursion with unregistered breakpoints

On 12/19/15, Jeff Merkey <linux.mdb@...il.com> wrote:
> On 12/19/15, Mike Galbraith <umgwanakikbuti@...il.com> wrote:
>> 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...
>>
>>
>>
>
> It matches the comments in the other section os code.  So what is
> wrong with this.  The rest of the file uses the exact same comment
> style.
>
> Please help me with this.
>
> Jeff
>

OK.  Somethings fritzed with how my emails are getting sent.  I just
create this, tested it,
and it applies PERFECTLY to my git clone.   Let me go back and try again.

Throw this one away.  try try again.

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/