Date: Tue, 6 Nov 2018 13:04:59 -0800 From: Andrew Morton <akpm@...ux-foundation.org> To: Rick Edgecombe <rick.p.edgecombe@...el.com> Cc: jeyu@...nel.org, willy@...radead.org, tglx@...utronix.de, mingo@...hat.com, hpa@...or.com, x86@...nel.org, linux-kernel@...r.kernel.org, linux-mm@...ck.org, kernel-hardening@...ts.openwall.com, daniel@...earbox.net, jannh@...gle.com, keescook@...omium.org, kristen@...ux.intel.com, dave.hansen@...el.com, arjan@...ux.intel.com Subject: Re: [PATCH v8 0/4] KASLR feature to randomize each loadable module On Fri, 2 Nov 2018 12:25:16 -0700 Rick Edgecombe <rick.p.edgecombe@...el.com> wrote: > This is V8 of the "KASLR feature to randomize each loadable module" patchset. > The purpose is to increase the randomization and also to make the modules > randomized in relation to each other instead of just the base, so that if one > module leaks the location of the others can't be inferred. I'm not seeing any info here which explains why we should add this to Linux. What is the end-user value? What problems does it solve? Are those problems real or theoretical? What are the exploit scenarios and how realistic are they? etcetera, etcetera. How are we to decide to buy this thing if we aren't given a glossy brochure? > There is a small allocation performance degradation versus v7 as a > trade off, but it is still faster on average than the existing > algorithm until >7000 modules. lol. How did you test 7000 modules? Using the selftest code?
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.