From: Jonathan Marek <jonathan@marek.ca>
To: Ard Biesheuvel <ardb@kernel.org>
Cc: Mark Rutland <mark.rutland@arm.com>,
Marc Zyngier <maz@kernel.org>,
"moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] arm64: set TEXT_OFFSET to 0x0 in preparation for removing it entirely
Date: Tue, 9 Jun 2020 08:52:42 -0400 [thread overview]
Message-ID: <63eebe9b-9aa8-addd-7965-df59b7237079@marek.ca> (raw)
In-Reply-To: <CAMj1kXF-eLc0RWmjfUYAk9BJ15-A5FwnPWo0nXoyqFQa3A62Mw@mail.gmail.com>
On 6/9/20 8:37 AM, Ard Biesheuvel wrote:
> On Tue, 9 Jun 2020 at 14:35, Jonathan Marek <jonathan@marek.ca> wrote:
>>
>> Hi,
>>
>> Just want to add that this patch also broke booting my arm64 kernel
>> (CONFIG_RANDOMIZE_BASE=n). This is on a recent qualcomm board.
>
> Which bootloader does it use?
>
abl/edk2
(https://source.codeaurora.org/quic/la/abl/tianocore/edk2/tree/?h=LA.UM.8.12.r1-11700-sm8250.0)
Just looking at it quickly (I am no bootloader expert), I think this may
have something to do with it:
https://source.codeaurora.org/quic/la/abl/tianocore/edk2/tree/QcomModulePkg/QcomModulePkg.dec?h=LA.UM.8.12.r1-11700-sm8250.0#n149
> I take it reverting the patch and enabling
> CONFIG_RANDOMIZE_TEXT_OFFSET makes it fail as well?
>
Yes, CONFIG_RANDOMIZE_TEXT_OFFSET also makes it fail.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-06-09 12:52 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-15 8:29 [PATCH] arm64: set TEXT_OFFSET to 0x0 in preparation for removing it entirely Ard Biesheuvel
2020-04-15 8:39 ` Will Deacon
2020-04-15 8:48 ` Ard Biesheuvel
2020-04-15 9:15 ` Will Deacon
2020-04-28 13:41 ` Will Deacon
2020-04-28 14:49 ` Will Deacon
2020-06-04 14:41 ` Marc Zyngier
2020-06-04 15:01 ` Will Deacon
2020-06-04 15:25 ` Marc Zyngier
2020-06-04 15:41 ` Ard Biesheuvel
2020-06-04 15:48 ` Ard Biesheuvel
2020-06-04 16:07 ` Marc Zyngier
2020-06-09 12:35 ` Jonathan Marek
2020-06-09 12:37 ` Ard Biesheuvel
2020-06-09 12:52 ` Jonathan Marek [this message]
2020-06-10 8:57 ` Mark Rutland
2020-06-10 9:25 ` 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=63eebe9b-9aa8-addd-7965-df59b7237079@marek.ca \
--to=jonathan@marek.ca \
--cc=ardb@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=maz@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;
as well as URLs for NNTP newsgroup(s).