linux-kernel - Re: [GIT PULL v4.5] 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 for Android: free password hash cracker in your pocket

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

Message-ID: <CALCETrWC3+SqDwC9vhLO=SM9buYAK2ujiS4wU2hXfSZmvFX0iA@mail.gmail.com>
Date:	Mon, 11 Jan 2016 18:19:41 -0800
From:	Andy Lutomirski <luto@...capital.net>
To:	Jeff Merkey <linux.mdb@...il.com>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	LKML <linux-kernel@...r.kernel.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <mingo@...hat.com>,
	"H. Peter Anvin" <hpa@...or.com>, X86 ML <x86@...nel.org>,
	Peter Zijlstra <peterz@...radead.org>,
	Andy Lutomirski <luto@...nel.org>,
	Masami Hiramatsu <masami.hiramatsu.pt@...achi.com>,
	Steven Rostedt <rostedt@...dmis.org>,
	Borislav Petkov <bp@...en8.de>, Jiri Olsa <jolsa@...nel.org>
Subject: Re: [GIT PULL v4.5] Fix INT1 recursion with unregistered breakpoints

On Mon, Jan 11, 2016 at 6:07 PM, Jeff Merkey <linux.mdb@...il.com> wrote:
> On 1/11/16, Andy Lutomirski <luto@...capital.net> wrote:
>> On Mon, Jan 11, 2016 at 5:30 PM, Jeff Merkey <linux.mdb@...il.com> wrote:
>>> On 1/11/16, Andy Lutomirski <luto@...capital.net> wrote:
>>>> On Mon, Jan 11, 2016 at 4:44 PM, Jeff Merkey <linux.mdb@...il.com>
>>>> wrote:
>>>>> Hi Thomas,
>>>>>
>>>>> I agree with #2, we should clear the breakpoint.  As for #1, if
>>>>> there's an execute breakpoint it MUST be cleared or it will just fire
>>>>> off again when it sees the iretd from the int1 exception handler.  I
>>>>> do use the breakpoint API Thomas, this showed up while debugging and
>>>>> testing the API with "lazy debug register switching".
>>>>>
>>>>> So do you want me to expand the patch and clear the breakpoint?  Just
>>>>> give the word and I'll get busy and GIT -R- DONE.
>>>>
>>>> It seems to me that you're papering over some issue instead of fixing
>>>> the root cause.  If you're using the API, then either you're doing it
>>>> wrong or the API is broken.  Can you figure out which and fix it?
>>>>
>>>> --Andy
>>>>
>>>
>>> Andy,
>>>
>>> Linux should not crash because someone triggered a breakpoint or one
>>> got triggered due to a program leaving some bits lying in a read only
>>> register (DR6) which for some strange reason someone in the linux
>>> world decided could be used as local storage and to pass arguments
>>> between subsystems - a register intel designed to be read from for
>>> status.    I did not design what's in that API, I have to live with
>>> it.
>>
>> The API appears to work, though.  Are you *sure* you're using it
>> correctly?  Are you telling the code in kernel/hw_breakpoint.c about
>> your breakpoint?
>>
>>> So all I am asking is that we fix this issue.  It does not matter
>>> to my debugger is this is fixed or not in Linux, since I carry the fix
>>> in my patch, but it does matter to the overall robustness of Linux.
>>
>> Robust against what, exactly?  What's the bug?
>>
>> I will grant that the comments about lazy dr7 switching are
>> mystifying, and cleaning them up might be nice.  But there's no
>> adequate explanation of what the failure mode is, how to trigger it,
>> or why your patch is a reasonable fix.  As it stands, you're
>> duplicating code.
>>
>> --Andy
>
> Andy,
>
> Couple of things:
>
> Would you like a copy of the test harness that creates this bug to
> test for yourself?  I previously posted it on the list.  If you don't
> have it, I'll provide it.

If you can send a short, buildable thing that triggers it, I'll read it.

>
> Since the dr6 bits get shifted around, it doesn't matter if the
> breakpoint was registered or not in the API because the broken handler
> will call NULL bp structures and crash whether its registered or not.
>

And what exactly does this have to do with anything?  Your patch is
all about spurious breakpoints triggered by dr7 and should have
nothing much to do with the value in dr6.  Unless dr6 is missing a bit
due to some issue, but you never suggested any problem like that.

> You keep asking the same questions and the answers are the the writeup
> for the patch, including how it is triggered, what triggers it, how I
> have triggered it, etc. and you are simply ignoring what's written
> there (or you have not read it).    It makes me wonder if you really
> know and understand x86 debugger stuff.
>

No, your writeup is long, hard to read, and doesn't address how any
actual problem exists.

--Andy