[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZS/FZAq6lbxXtBtB@gmail.com>
Date: Wed, 18 Oct 2023 13:45:40 +0200
From: Ingo Molnar <mingo@...nel.org>
To: "H. Peter Anvin" <hpa@...or.com>,
Kristen Carlson Accardi <kristen@...ux.intel.com>
Cc: Hou Wenlong <houwenlong.hwl@...group.com>,
linux-kernel@...r.kernel.org,
Lai Jiangshan <jiangshan.ljs@...group.com>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>, Borislav Petkov <bp@...en8.de>,
Dave Hansen <dave.hansen@...ux.intel.com>,
"maintainer:X86 ARCHITECTURE 32-BIT AND 64-BIT" <x86@...nel.org>,
Josh Poimboeuf <jpoimboe@...nel.org>,
Anshuman Khandual <anshuman.khandual@....com>,
Mike Rapoport <rppt@...nel.org>,
Pasha Tatashin <pasha.tatashin@...een.com>
Subject: Re: [PATCH RFC 1/7] x86/head/64: Mark startup_gdt and
startup_gdt_descr as __initdata
* H. Peter Anvin <hpa@...or.com> wrote:
> If the goal is better KASLR, then what we really should spend time on was
> Kristen Accardi's fgKASLR patches, which not only exponentially(!)
> increases the randomization entrophy but also *actually* avoids the "one
> leak and it's over" problem.
Agreed. Going by this version of function-granularity KASLR from 3 years
ago:
https://lwn.net/Articles/824307/
https://lwn.net/ml/linux-kernel/20200623172327.5701-1-kristen@linux.intel.com/
The fgKASLR feature looks entirely viable to me. Back then I presumed it
would get iterated beyond v3, and then it fell off my radar. :-/
If Kristen or someone else would like to dust this off & submit a fresh
version it would be much appreciated!
Thanks,
Ingo
Powered by blists - more mailing lists