linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: catalin.marinas@arm.com (Catalin Marinas)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 0/3] arm64: EFI stub isolation
Date: Thu, 8 Oct 2015 18:19:51 +0100	[thread overview]
Message-ID: <20151008171950.GP17192@e104818-lin.cambridge.arm.com> (raw)
In-Reply-To: <1444129424-8284-1-git-send-email-ard.biesheuvel@linaro.org>

On Tue, Oct 06, 2015 at 12:03:41PM +0100, Ard Biesheuvel wrote:
> We need to ensure that the EFI stub only uses parts of the kernel proper
> that are safe to use when the kernel virtual mapping is not active yet.
> 
> So move all C code dependencies to the libstub, and do a verification pass
> to ensure that no absolute relocations are used.
> 
> On the arm64 side, annotate all the stub's dependencies as safe for PI
> (position independent
[...]
> Ard Biesheuvel (3):
>   arm64/efi: remove /chosen/linux,uefi-stub-kern-ver DT property
>   arm64: use ENDPIPROC() to annotate position independent assembler
>     routines
>   arm64/efi: isolate EFI stub from the kernel proper

The patches look fine to me. I haven't tested them yet since they don't
apply to the arm64 for-next/core cleanly and you said you are going to
repost the series anyway. I'll wait.

-- 
Catalin

      parent reply	other threads:[~2015-10-08 17:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-06 11:03 [PATCH v3 0/3] arm64: EFI stub isolation Ard Biesheuvel
2015-10-06 11:03 ` [PATCH v3 1/3] arm64/efi: remove /chosen/linux, uefi-stub-kern-ver DT property Ard Biesheuvel
2015-10-13  1:18   ` Roy Franz
2015-10-06 11:03 ` [PATCH v3 2/3] arm64: use ENDPIPROC() to annotate position independent assembler routines Ard Biesheuvel
2015-10-06 11:03 ` [PATCH v3 3/3] arm64/efi: isolate EFI stub from the kernel proper Ard Biesheuvel
2015-10-08 17:19 ` Catalin Marinas [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=20151008171950.GP17192@e104818-lin.cambridge.arm.com \
    --to=catalin.marinas@arm.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;
as well as URLs for NNTP newsgroup(s).