linux-kernel - [PATCH 0/1] Selecting Load Addresses According to p

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <20200724172016.608742-1-ckennelly@google.com>
Date:   Fri, 24 Jul 2020 13:20:15 -0400
From:   Chris Kennelly <ckennelly@...gle.com>
To:     Alexey Dobriyan <adobriyan@...il.com>,
        Song Liu <songliubraving@...com>,
        David Rientjes <rientjes@...gle.com>,
        Ian Rogers <irogers@...gle.com>, linux-fsdevel@...r.kernel.org,
        linux-kernel@...r.kernel.org
Cc:     Chris Kennelly <ckennelly@...gle.com>
Subject: [PATCH 0/1] Selecting Load Addresses According to p_align

The current ELF loading mechancism provides page-aligned mappings.  This
can lead to the program being loaded in a way unsuitable for
file-backed, transparent huge pages when handling PIE executables.

While specifying -z,max-page-size=0x200000 to the linker will generate
suitably aligned segments for huge pages on x86_64, the executable needs
to be loaded at a suitably aligned address as well.  This alignment
requires the binary's cooperation, as distinct segments need to be
appropriately paddded to be eligible for THP.

For binaries built with increased alignment, this limits the number of
bits usable for ASLR, but provides some randomization over using fixed
load addresses/non-PIE binaries.

Chris Kennelly (1):
  fs/binfmt_elf: Use PT_LOAD p_align values for suitable start address.

 fs/binfmt_elf.c | 24 ++++++++++++++++++++++++
 1 file changed, 24 insertions(+)

-- 
2.28.0.rc0.105.gf9edc3c819-goog