linux-kernel - IST stack patches v3.5

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-next>] [day] [month] [year] [list]

Message-ID: <CALCETrWS6-DAyQyHbouXqgEwmaOjxMhFGudV7zsXb9_-mK2TPQ@mail.gmail.com>
Date:	Mon, 24 Nov 2014 17:52:34 -0800
From:	Andy Lutomirski <luto@...capital.net>
To:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	X86 ML <x86@...nel.org>, Borislav Petkov <bp@...en8.de>,
	Tony Luck <tony.luck@...el.com>,
	Andi Kleen <andi@...stfloor.org>
Cc:	Paul McKenney <paulmck@...ux.vnet.ibm.com>
Subject: IST stack patches v3.5

I've tagged v3.5 of my paranoid stack code.  It's in a strange state right now:

Patch 1 (the actual stack switching) is standalone.  It's not really a
good base for the memory failure stuff, because all of the ist_enter
stuff is missing.  It should *work*, but the result will be ugly.
OTOH, it should be okay as a base for fsgsbase.

Patch 2 is from Paul McKenney.  It fixes RCU NMI nesting, which is a
prerequisite for ist_enter.  I think that the current plan is for that
to happen in 3.20.  Speak up if you want it sooner.

Patch 4 is purely for testing.  It forces "NMIs" to nest.

"x86, mce: Improve timeout error messages" is in there so I don't
forget about it.  Tony and Borislav, if you like it, want to pick it
up?  It really has very little to do with the rest of this code.

The remainder of the non-atomic IST stuff is in there in a plausibly
final form, but it's oddly based.

--Andy

-- 
Andy Lutomirski
AMA Capital Management, LLC
--
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/