From: riel@redhat.com To: linux-kernel@vger.kernel.org Cc: kernel-hardening@lists.openwall.com, akpm@linux-foundation.org, mingo@kernel.org, oleg@redhat.com, lwoodman@redhat.com, mhocko@suse.de, danielmicay@gmail.com, will.deacon@arm.com, benh@kernel.crashing.org Subject: [PATCH 1/6] binfmt_elf: document load_bias a little bit Date: Fri, 2 Jun 2017 11:20:05 -0400 [thread overview] Message-ID: <20170602152010.2064-2-riel@redhat.com> (raw) In-Reply-To: <20170602152010.2064-1-riel@redhat.com> From: Rik van Riel <riel@redhat.com> After me and another unnamed developer got confused by the subtraction of vaddr in this branch of the code, followed by adding vaddr back in a little bit later, for the third time, maybe it is time to document this quirky bit of code. Signed-off-by: Rik van Riel <riel@redhat.com> --- fs/binfmt_elf.c | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/fs/binfmt_elf.c b/fs/binfmt_elf.c index 5075fd5c62c8..8c3f4dbc7603 100644 --- a/fs/binfmt_elf.c +++ b/fs/binfmt_elf.c @@ -930,10 +930,16 @@ static int load_elf_binary(struct linux_binprm *bprm) if (loc->elf_ex.e_type == ET_EXEC || load_addr_set) { elf_flags |= MAP_FIXED; } else if (loc->elf_ex.e_type == ET_DYN) { - /* Try and get dynamic programs out of the way of the + /* + * Try and get dynamic programs out of the way of the * default mmap base, as well as whatever program they * might try to exec. This is because the brk will - * follow the loader, and is not movable. */ + * follow the loader, and is not movable. + * + * The load_bias is the difference between the address + * in the elf header and the address where the binary + * is mmapped. + */ load_bias = ELF_ET_DYN_BASE - vaddr; if (current->flags & PF_RANDOMIZE) load_bias += arch_mmap_rnd(); -- 2.9.3
WARNING: multiple messages have this Message-ID (diff)
From: riel@redhat.com To: linux-kernel@vger.kernel.org Cc: kernel-hardening@lists.openwall.com, akpm@linux-foundation.org, mingo@kernel.org, oleg@redhat.com, lwoodman@redhat.com, mhocko@suse.de, danielmicay@gmail.com, will.deacon@arm.com, benh@kernel.crashing.org Subject: [kernel-hardening] [PATCH 1/6] binfmt_elf: document load_bias a little bit Date: Fri, 2 Jun 2017 11:20:05 -0400 [thread overview] Message-ID: <20170602152010.2064-2-riel@redhat.com> (raw) In-Reply-To: <20170602152010.2064-1-riel@redhat.com> From: Rik van Riel <riel@redhat.com> After me and another unnamed developer got confused by the subtraction of vaddr in this branch of the code, followed by adding vaddr back in a little bit later, for the third time, maybe it is time to document this quirky bit of code. Signed-off-by: Rik van Riel <riel@redhat.com> --- fs/binfmt_elf.c | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/fs/binfmt_elf.c b/fs/binfmt_elf.c index 5075fd5c62c8..8c3f4dbc7603 100644 --- a/fs/binfmt_elf.c +++ b/fs/binfmt_elf.c @@ -930,10 +930,16 @@ static int load_elf_binary(struct linux_binprm *bprm) if (loc->elf_ex.e_type == ET_EXEC || load_addr_set) { elf_flags |= MAP_FIXED; } else if (loc->elf_ex.e_type == ET_DYN) { - /* Try and get dynamic programs out of the way of the + /* + * Try and get dynamic programs out of the way of the * default mmap base, as well as whatever program they * might try to exec. This is because the brk will - * follow the loader, and is not movable. */ + * follow the loader, and is not movable. + * + * The load_bias is the difference between the address + * in the elf header and the address where the binary + * is mmapped. + */ load_bias = ELF_ET_DYN_BASE - vaddr; if (current->flags & PF_RANDOMIZE) load_bias += arch_mmap_rnd(); -- 2.9.3
next prev parent reply other threads:[~2017-06-02 15:20 UTC|newest] Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top 2017-06-02 15:20 [PATCH 0/6] move mmap_area and PIE binaries away from the stack riel 2017-06-02 15:20 ` [kernel-hardening] " riel 2017-06-02 15:20 ` riel [this message] 2017-06-02 15:20 ` [kernel-hardening] [PATCH 1/6] binfmt_elf: document load_bias a little bit riel 2017-06-02 19:27 ` Kees Cook 2017-06-02 19:27 ` Kees Cook 2017-06-02 15:20 ` [PATCH 2/6] x86/elf: move 32 bit ELF_ET_DYN_BASE to 256MB riel 2017-06-02 15:20 ` [kernel-hardening] " riel 2017-06-03 4:22 ` Kees Cook 2017-06-03 4:22 ` [kernel-hardening] " Kees Cook 2017-06-03 11:57 ` Daniel Micay 2017-06-03 11:57 ` [kernel-hardening] " Daniel Micay 2017-06-05 13:54 ` Rik van Riel 2017-06-05 13:54 ` [kernel-hardening] " Rik van Riel 2017-06-02 15:20 ` [PATCH 3/6] x86/mmap: properly account for stack randomization in mmap_base riel 2017-06-02 15:20 ` [kernel-hardening] " riel 2017-06-03 4:46 ` Kees Cook 2017-06-03 4:46 ` Kees Cook 2017-06-03 12:16 ` Daniel Micay 2017-06-03 12:16 ` Daniel Micay 2017-06-02 15:20 ` [PATCH 4/6] arm64/mmap: " riel 2017-06-02 15:20 ` [kernel-hardening] " riel 2017-06-02 15:20 ` [PATCH 5/6] arm64: move COMPAT_ELF_ET_DYN_BASE lower in the address space riel 2017-06-02 15:20 ` [kernel-hardening] " riel 2017-06-02 15:20 ` [PATCH 6/6] powerpc,mmap: properly account for stack randomization in mmap_base riel 2017-06-02 15:20 ` [kernel-hardening] " riel 2017-06-03 4:37 ` [kernel-hardening] [PATCH 0/6] move mmap_area and PIE binaries away from the stack Kees Cook 2017-06-03 4:37 ` Kees Cook 2017-06-03 12:14 ` Daniel Micay 2017-06-03 12:14 ` Daniel Micay
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=20170602152010.2064-2-riel@redhat.com \ --to=riel@redhat.com \ --cc=akpm@linux-foundation.org \ --cc=benh@kernel.crashing.org \ --cc=danielmicay@gmail.com \ --cc=kernel-hardening@lists.openwall.com \ --cc=linux-kernel@vger.kernel.org \ --cc=lwoodman@redhat.com \ --cc=mhocko@suse.de \ --cc=mingo@kernel.org \ --cc=oleg@redhat.com \ --cc=will.deacon@arm.com \ /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: linkBe 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.