Date: Thu, 7 Feb 2019 09:01:57 -0800 From: Thomas Garnier <thgarnie@...omium.org> To: Borislav Petkov <bp@...en8.de> Cc: Kernel Hardening <kernel-hardening@...ts.openwall.com>, Kristen Carlson Accardi <kristen@...ux.intel.com>, Herbert Xu <herbert@...dor.apana.org.au>, "David S. Miller" <davem@...emloft.net>, Thomas Gleixner <tglx@...utronix.de>, Ingo Molnar <mingo@...hat.com>, "H. Peter Anvin" <hpa@...or.com>, "the arch/x86 maintainers" <x86@...nel.org>, Linux Crypto Mailing List <linux-crypto@...r.kernel.org>, LKML <linux-kernel@...r.kernel.org> Subject: Re: [PATCH v6 01/27] x86/crypto: Adapt assembly for PIE support On Thu, Feb 7, 2019 at 3:49 AM Borislav Petkov <bp@...en8.de> wrote: > > On Thu, Jan 31, 2019 at 11:24:08AM -0800, Thomas Garnier wrote: > > Change the assembly code to use only relative references of symbols for the > > kernel to be PIE compatible. > > > > Position Independent Executable (PIE) support will allow to extend the > > KASLR randomization range below 0xffffffff80000000. > > This sentence is auto-sprinkled in a bunch of commit messages. Sounds to > me it should be rather somewhere in the 0/n message as a justification > for the feature but not in every other commit message...? I go into more details in the compose message but I wanted a small sentence explaining why PIE changes are being made. > > -- > Regards/Gruss, > Boris. > > Good mailing practices for 400: avoid top-posting and trim the reply.
Powered by blists - more mailing lists
Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.