From: Kefeng Wang <wangkefeng.wang@huawei.com>
To: Ard Biesheuvel <ardb@kernel.org>
Cc: Will Deacon <will@kernel.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
linux-efi <linux-efi@vger.kernel.org>,
Mark Rutland <mark.rutland@arm.com>
Subject: Re: [Question] Should retain 2M alignment if kernel image is bad aligned at entry or BSS overlaps?
Date: Fri, 4 Mar 2022 00:03:04 +0800 [thread overview]
Message-ID: <be55d15c-d5a7-8ef0-3cb1-ecf705b260e1@huawei.com> (raw)
In-Reply-To: <CAMj1kXEUk5ofQvmi8C7A=QX28KO7KfR665ji__AcRL39MP014A@mail.gmail.com>
On 2022/3/3 19:31, Ard Biesheuvel wrote:
> On Thu, 3 Mar 2022 at 06:14, Kefeng Wang <wangkefeng.wang@huawei.com> wrote:
>>
>> On 2022/3/1 20:57, Ard Biesheuvel wrote:
>>> On Tue, 1 Mar 2022 at 11:34, Kefeng Wang <wangkefeng.wang@huawei.com> wrote:
> ...
>>>> Do you think the following adjustment make sense or it is definitely wrong?
>>>>
>>> I can only answer this if I understand which problem it solves. Why do
>>> you need the 2M alignment in this case?
>>> .
>> Sorry for the late response，my purpose is that we don't want to enable
>> KPTI if
>>
>> KASLR is disabled. For now, if there are some firmware bug, the kernel
>> image is
>>
>> relocated which lead to kaslr_requires_kpti() returen
>> ture(kaslr_offset() > 0).
>>
>> the change to 2M alignment is a workaround and according to your
>> explanation,
>>
>> I don't think the workaround is necessary. I want to make sure that the
>> above
>>
>> scene is expected? thanks.
>>
> I don't think we need this.
Got it, thanks.
> .
prev parent reply other threads:[~2022-03-03 16:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-01 6:49 [Question] Should retain 2M alignment if kernel image is bad aligned at entry or BSS overlaps? Kefeng Wang
2022-03-01 7:22 ` Ard Biesheuvel
2022-03-01 10:34 ` Kefeng Wang
2022-03-01 12:57 ` Ard Biesheuvel
2022-03-03 6:14 ` Kefeng Wang
2022-03-03 11:31 ` Ard Biesheuvel
2022-03-03 16:03 ` Kefeng Wang [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=be55d15c-d5a7-8ef0-3cb1-ecf705b260e1@huawei.com \
--to=wangkefeng.wang@huawei.com \
--cc=ardb@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-efi@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=will@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