Openwall GNU/*/Linux - a small security-enhanced Linux distro for servers
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Tue, 6 Aug 2019 17:43:47 +0200
From: Borislav Petkov <>
To: Thomas Garnier <>
Cc:,,, Herbert Xu <>,
	"David S. Miller" <>,
	Thomas Gleixner <>,
	Ingo Molnar <>, "H. Peter Anvin" <>,, Andy Lutomirski <>,
	Juergen Gross <>,
	Thomas Hellstrom <>,
	"VMware, Inc." <>,
	"Rafael J. Wysocki" <>,
	Len Brown <>, Pavel Machek <>,
	Peter Zijlstra <>,
	Nadav Amit <>, Jann Horn <>,
	Feng Tang <>,
	Maran Wilson <>,
	Enrico Weigelt <>,
	Allison Randal <>,
	Alexios Zavras <>,,,,
Subject: Re: [PATCH v9 00/11] x86: PIE support to extend KASLR randomization

On Tue, Jul 30, 2019 at 12:12:44PM -0700, Thomas Garnier wrote:
> These patches make some of the changes necessary to build the kernel as
> Position Independent Executable (PIE) on x86_64. Another patchset will
> add the PIE option and larger architecture changes.

Yeah, about this: do we have a longer writeup about the actual benefits
of all this and why we should take this all? After all, after looking
at the first couple of asm patches, it is posing restrictions to how
we deal with virtual addresses in asm (only RIP-relative addressing in
64-bit mode, MOVs with 64-bit immediates, etc, for example) and I'm
willing to bet money that some future unrelated change will break PIE
sooner or later. And I'd like to have a better justification why we
should enforce those new "rules" unconditionally.



Good mailing practices for 400: avoid top-posting and trim the reply.

Powered by blists - more mailing lists

Your e-mail address:

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.