From: "H. Peter Anvin" <hpa@zytor.com>
To: David Daney <david.daney@cavium.com>
Cc: linux-mips@linux-mips.org, ralf@linux-mips.org,
linux-kernel@vger.kernel.org,
Russell King <linux@arm.linux.org.uk>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>,
x86@kernel.org, Alexander Viro <viro@zeniv.linux.org.uk>,
linux-arm-kernel@lists.infradead.org,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 1/2] fs: binfmt_elf: Create Kconfig variable for PIE randomization.
Date: Wed, 09 Nov 2011 16:37:43 -0800 [thread overview]
Message-ID: <4EBB1CD7.6040502@zytor.com> (raw)
In-Reply-To: <1320885178-24201-1-git-send-email-david.daney@cavium.com>
On 11/09/2011 04:32 PM, David Daney wrote:
> Randomization of PIE load address is hard coded in binfmt_elf.c for
> X86 and ARM. Create a new Kconfig variable
> (CONFIG_ARCH_BINFMT_ELF_RANDOMIZE_PIE) for this and use it instead.
> Thus architecture specific policy is pushed out of the generic
> binfmt_elf.c and into the architecture Kconfig files.
>
> X86 and ARM Kconfigs are modified to select the new variable so there
> is no change in behavior. A follow on patch will select it for MIPS
> too.
>
> Cc: Russell King <linux@arm.linux.org.uk>
> Cc: Thomas Gleixner <tglx@linutronix.de>
> Cc: Ingo Molnar <mingo@redhat.com>
> Cc: "H. Peter Anvin" <hpa@zytor.com>
> Cc: x86@kernel.org
> Cc: Alexander Viro <viro@zeniv.linux.org.uk>
> Cc: linux-arm-kernel@lists.infradead.org
> Cc: linux-kernel@vger.kernel.org
> Cc: linux-fsdevel@vger.kernel.org
> Signed-off-by: David Daney <david.daney@cavium.com>
Acked-by: H. Peter Anvin <hpa@zytor.com>
prev parent reply other threads:[~2011-11-10 0:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-10 0:32 [PATCH 1/2] fs: binfmt_elf: Create Kconfig variable for PIE randomization David Daney
2011-11-10 0:32 ` [PATCH 2/2] MIPS: Randomize PIE load address David Daney
2011-11-10 0:37 ` H. Peter Anvin [this message]
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=4EBB1CD7.6040502@zytor.com \
--to=hpa@zytor.com \
--cc=david.daney@cavium.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=linux@arm.linux.org.uk \
--cc=mingo@redhat.com \
--cc=ralf@linux-mips.org \
--cc=tglx@linutronix.de \
--cc=viro@zeniv.linux.org.uk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox