linux-kernel - Re: [PATCH 4/5] x86: Allow nesting of the debug stack IDT setting

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]

Message-ID: <1338497811.13348.443.camel@gandalf.stny.rr.com>
Date:	Thu, 31 May 2012 16:56:51 -0400
From:	Steven Rostedt <rostedt@...dmis.org>
To:	"H. Peter Anvin" <hpa@...or.com>
Cc:	linux-kernel@...r.kernel.org, Ingo Molnar <mingo@...e.hu>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Peter Zijlstra <peterz@...radead.org>,
	Frederic Weisbecker <fweisbec@...il.com>,
	Masami Hiramatsu <masami.hiramatsu.pt@...achi.com>,
	Dave Jones <davej@...hat.com>, Andi Kleen <ak@...ux.intel.com>
Subject: Re: [PATCH 4/5] x86: Allow nesting of the debug stack IDT setting

On Thu, 2012-05-31 at 13:39 -0700, H. Peter Anvin wrote:
> On 05/31/2012 01:35 PM, Steven Rostedt wrote:
> > 
> > Thus only the debug stack does the stack TSS trick.
> > 
> > Is this what you were looking for? (God, it just shows how much time
> > I've been spending on this crap, as I was able to find all this by
> > memory and not grepping for it :-p )
> > 
> 
> That's why I asked instead of pulled it up myself.
> 
> However, what is missing is what the permitted transitions are.  This
> affects the options.

Only the debug stack changes. These happen in the two places I already
mentioned.

One, the switch of the IDT in NMI (to convert the IST from 4 to 0, and
just keep the same stack).

Two, is the trick in the paranoidzeroentry_ist code (adding the debug
stack). That changes the DEBUG stack pointer.

-- Steve


--
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/