From: Andrew Morton <akpm@linux-foundation.org>
To: Rick Edgecombe <rick.p.edgecombe@intel.com>
Cc: jeyu@kernel.org, willy@infradead.org, tglx@linutronix.de,
mingo@redhat.com, hpa@zytor.com, x86@kernel.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
kernel-hardening@lists.openwall.com, daniel@iogearbox.net,
jannh@google.com, keescook@chromium.org, kristen@linux.intel.com,
dave.hansen@intel.com, arjan@linux.intel.com
Subject: Re: [PATCH v8 0/4] KASLR feature to randomize each loadable module
Date: Tue, 6 Nov 2018 13:04:59 -0800 [thread overview]
Message-ID: <20181106130459.7a2669604a2c274edbe25971@linux-foundation.org> (raw)
In-Reply-To: <20181102192520.4522-1-rick.p.edgecombe@intel.com>
On Fri, 2 Nov 2018 12:25:16 -0700 Rick Edgecombe <rick.p.edgecombe@intel.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?
next prev parent reply other threads:[~2018-11-06 21:05 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-02 19:25 [PATCH v8 0/4] KASLR feature to randomize each loadable module Rick Edgecombe
2018-11-02 19:25 ` [PATCH v8 1/4] vmalloc: Add __vmalloc_node_try_addr function Rick Edgecombe
2018-11-06 21:05 ` Andrew Morton
2018-11-07 20:03 ` Edgecombe, Rick P
2018-11-07 20:03 ` Edgecombe, Rick P
2018-11-02 19:25 ` [PATCH v8 2/4] x86/modules: Increase randomization for modules Rick Edgecombe
2018-11-06 21:05 ` Andrew Morton
2018-11-07 20:03 ` Edgecombe, Rick P
2018-11-07 20:03 ` Edgecombe, Rick P
2018-11-02 19:25 ` [PATCH v8 3/4] vmalloc: Add debugfs modfraginfo Rick Edgecombe
2018-11-02 19:25 ` [PATCH v8 4/4] Kselftest for module text allocation benchmarking Rick Edgecombe
2018-11-02 19:25 ` Rick Edgecombe
2018-11-06 21:05 ` Andrew Morton
2018-11-06 21:05 ` Andrew Morton
2018-11-07 20:03 ` Edgecombe, Rick P
2018-11-07 20:03 ` Edgecombe, Rick P
2018-11-06 21:04 ` Andrew Morton [this message]
2018-11-07 20:03 ` [PATCH v8 0/4] KASLR feature to randomize each loadable module Edgecombe, Rick P
2018-11-07 20:03 ` Edgecombe, Rick P
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20181106130459.7a2669604a2c274edbe25971@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=arjan@linux.intel.com \
--cc=daniel@iogearbox.net \
--cc=dave.hansen@intel.com \
--cc=hpa@zytor.com \
--cc=jannh@google.com \
--cc=jeyu@kernel.org \
--cc=keescook@chromium.org \
--cc=kernel-hardening@lists.openwall.com \
--cc=kristen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@redhat.com \
--cc=rick.p.edgecombe@intel.com \
--cc=tglx@linutronix.de \
--cc=willy@infradead.org \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.