From: mlangsdo@redhat.com (Mark Langsdorf)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH 0/3] arm64 initrd mapping/relocation
Date: Tue, 2 Feb 2016 15:39:11 -0600 [thread overview]
Message-ID: <56B121FF.8040707@redhat.com> (raw)
In-Reply-To: <20160202180622.GP10166@arm.com>
On 02/02/2016 12:06 PM, Will Deacon wrote:
> On Tue, Feb 02, 2016 at 06:56:39PM +0100, Ard Biesheuvel wrote:
>> After discussing in linux-efi with Mark, and on #armlinux with Will, this is
>> a proposal for dealing with initrd memory that is potentially not covered by
>> the linear region.
>>
>> Note that this will look slightly differently when some of the KASLR work gets
>> merged, but this should only affect the way we deal with the initrd if it sits
>> outside of the linear region.
>>
>> Mostly intended for discussion, not tested at all.
>
> Thanks Ard, this looks like a much better approach to me. Mark -- does
> the general idea work for you too?
I'm not quite the right Mark but Mark Salter is on vacation
and I was the one who discovered this bug. These patches
do fix the problem and it looks like they tidy up some
code. Will they be in v4.5-rc3?
--Mark Langsdorf
next prev parent reply other threads:[~2016-02-02 21:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-02 17:56 [RFC PATCH 0/3] arm64 initrd mapping/relocation Ard Biesheuvel
2016-02-02 17:56 ` [RFC PATCH 1/3] memblock: add routine to clear the MEMBLOCK_NOMAP flag for a region Ard Biesheuvel
2016-02-02 17:56 ` [RFC PATCH 2/3] arm64: add the initrd region to the linear mapping explicitly Ard Biesheuvel
2016-02-02 17:56 ` [RFC PATCH 3/3] arm64: remove the now unneeded relocate_initrd() Ard Biesheuvel
2016-02-02 18:06 ` [RFC PATCH 0/3] arm64 initrd mapping/relocation Will Deacon
2016-02-02 21:39 ` Mark Langsdorf [this message]
2016-02-03 14:22 ` Mark Salter
2016-02-03 14:26 ` Ard Biesheuvel
2016-02-08 16:17 ` Jeremy Linton
2016-02-02 21:39 ` Mark Langsdorf
2016-02-03 8:42 ` Ard Biesheuvel
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=56B121FF.8040707@redhat.com \
--to=mlangsdo@redhat.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 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.