linux-kernel - Re: [PATCH v2 09/36] x86/asm: Re-add manual CFI infrastructure

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: <20151008141449.GA29358@gmail.com>
Date:	Thu, 8 Oct 2015 16:14:49 +0200
From:	Ingo Molnar <mingo@...nel.org>
To:	Borislav Petkov <bp@...en8.de>
Cc:	Andy Lutomirski <luto@...capital.net>,
	Andy Lutomirski <luto@...nel.org>, X86 ML <x86@...nel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Brian Gerst <brgerst@...il.com>,
	Denys Vlasenko <dvlasenk@...hat.com>,
	Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: [PATCH v2 09/36] x86/asm: Re-add manual CFI infrastructure


* Borislav Petkov <bp@...en8.de> wrote:

> On Tue, Oct 06, 2015 at 11:21:41AM -0700, Andy Lutomirski wrote:
>
> > OK, I'll strip out the push, movq, etc stuff for v3.  I'll leave all of the 
> > CFI_XYZ macros, even the unused one, because that's only a couple of lines of 
> > code and they all have very simple and obvious meanings (or as simple as the 
> > underlying directives, anyway).
> 
> If they're going to be used by the vDSO only, maybe they all should go into a 
> header which is private to the vDSO only so that people don't get any ideas and 
> the gunk starts spreading again...

Yeah. So for the vDSO code itself it's an obvious step forward: replacing black 
magic hexa encodings with symbolic directives.

Thanks,

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