linux-kernel - [PATCH 0/3] x86_64: Merge (paranoid)?(zero|error)entry(

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]

Date:	Wed, 21 May 2014 15:07:06 -0700
From:	Andy Lutomirski <luto@...capital.net>
To:	x86@...nel.org, "H. Peter Anvin" <hpa@...or.com>
Cc:	Borislav Petkov <bp@...en8.de>, Jiri Kosina <jkosina@...e.cz>,
	Thomas Gleixner <tglx@...utronix.de>,
	Steven Rostedt <rostedt@...dmis.org>,
	Andi Kleen <andi@...stfloor.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Ingo Molnar <mingo@...nel.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Andy Lutomirski <luto@...capital.net>
Subject: [PATCH 0/3] x86_64: Merge (paranoid)?(zero|error)entry(_idt)?

Inspired by the RET vs IRET discussion, I thought about how much of a
mess the current entry macros are and I shuddered at the thought of
trying to modify them.

This little series merges them all into one idtentry macro that has
arguments that specify all the various weird behaviors.  It has a major
benefit: you can now look at the code and see how, say, the
has_error_code and !has_error_code cases differ.

Andy Lutomirski (3):
  x86_64: Add missing 'DEFAULT_FRAME 0' entry annotations
  x86_64: Merge most 64-bit asm entry macros
  x86_64: Merge paranoidzeroentry_ist into idtentry

 arch/x86/kernel/entry_64.S | 185 ++++++++++++++++++++-------------------------
 1 file changed, 80 insertions(+), 105 deletions(-)

-- 
1.9.0

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