public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: trini@ti.com (Tom Rini)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv2 4/4] arm64: Enable TEXT_OFFSET fuzzing
Date: Fri, 30 May 2014 09:22:08 -0400	[thread overview]
Message-ID: <20140530132208.GA5836@bill-the-cat> (raw)
In-Reply-To: <1401196710-6290-5-git-send-email-mark.rutland@arm.com>

On Tue, May 27, 2014 at 02:18:30PM +0100, Mark Rutland wrote:

> The arm64 Image header contains a text_offset field which bootloaders
> are supposed to read to determine the offset (from a 2MB aligned "start
> of memory" per booting.txt) at which to load the kernel. The offset is
> not well respected by bootloaders at present, and due to the lack of
> variation there is little incentive to support it. This is unfortunate
> for the sake of future kernels where we may wish to vary the text offset
> (even zeroing it).
> 
> This patch adds options to arm64 to enable fuzz-testing of text_offset.
> CONFIG_ARM64_RANDOMIZE_TEXT_OFFSET forces the text offset to a random
> 16-byte aligned value value in the range [0..2MB) upon a build of the
> kernel. It is recommended that distribution kernels enable randomization
> to test bootloaders such that any compliance issues can be fixed early.
> 
> Signed-off-by: Mark Rutland <mark.rutland@arm.com>

Acked-by: Tom Rini <trini@ti.com>

-- 
Tom

      reply	other threads:[~2014-05-30 13:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-27 13:18 [PATCHv2 0/4] arm64: simplify restrictions on bootloaders Mark Rutland
2014-05-27 13:18 ` [PATCHv2 1/4] arm64: head.S: remove unnecessary function alignment Mark Rutland
2014-05-27 13:18 ` [PATCHv2 2/4] arm64: place initial page tables above the kernel Mark Rutland
2014-05-27 13:18 ` [PATCHv2 3/4] arm64: export effective Image size to bootloaders Mark Rutland
2014-05-27 13:18 ` [PATCHv2 4/4] arm64: Enable TEXT_OFFSET fuzzing Mark Rutland
2014-05-30 13:22   ` Tom Rini [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=20140530132208.GA5836@bill-the-cat \
    --to=trini@ti.com \
    --cc=linux-arm-kernel@lists.infradead.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