From: Will Deacon <will@kernel.org>
To: linux-arm-kernel@lists.infradead.org,
Barry Song <song.bao.hua@hisilicon.com>,
catalin.marinas@arm.com
Cc: kernel-team@android.com, Will Deacon <will@kernel.org>,
linux@roeck-us.net, tyhicks@linux.microsoft.com,
Qi Liu <liuqi115@huawei.com>,
linuxarm@huawei.com, maz@kernel.org,
Ard Biesheuvel <ard.biesheuvel@arm.com>,
tabba@google.com, Masami Hiramatsu <mhiramat@kernel.org>,
lecopzer.chen@mediatek.com, mark.rutland@arm.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] arm64: fix the doc of RANDOMIZE_MODULE_REGION_FULL
Date: Tue, 3 Aug 2021 11:05:20 +0100 [thread overview]
Message-ID: <162798340286.1497797.18069753288714137637.b4-ty@kernel.org> (raw)
In-Reply-To: <20210730125131.13724-1-song.bao.hua@hisilicon.com>
On Sat, 31 Jul 2021 00:51:31 +1200, Barry Song wrote:
> Obviously kaslr is setting the module region to 2GB rather than 4GB since
> commit b2eed9b588112 ("arm64/kernel: kaslr: reduce module randomization
> range to 2 GB"). So fix the size of region in Kconfig.
> On the other hand, even though RANDOMIZE_MODULE_REGION_FULL is not set,
> module_alloc() can fall back to a 2GB window if ARM64_MODULE_PLTS is set.
> In this case, veneers are still needed. !RANDOMIZE_MODULE_REGION_FULL
> doesn't necessarily mean veneers are not needed.
> So fix the doc to be more precise to avoid any confusion to the readers
> of the code.
Applied to arm64 (for-next/fixes), thanks!
[1/1] arm64: fix the doc of RANDOMIZE_MODULE_REGION_FULL
https://git.kernel.org/arm64/c/f9c4ff2ab9fe
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
prev parent reply other threads:[~2021-08-03 10:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-30 12:51 [PATCH v2] arm64: fix the doc of RANDOMIZE_MODULE_REGION_FULL Barry Song
2021-07-31 0:28 ` Masami Hiramatsu
2021-08-03 10:05 ` Will Deacon [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=162798340286.1497797.18069753288714137637.b4-ty@kernel.org \
--to=will@kernel.org \
--cc=ard.biesheuvel@arm.com \
--cc=catalin.marinas@arm.com \
--cc=kernel-team@android.com \
--cc=lecopzer.chen@mediatek.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=linuxarm@huawei.com \
--cc=liuqi115@huawei.com \
--cc=mark.rutland@arm.com \
--cc=maz@kernel.org \
--cc=mhiramat@kernel.org \
--cc=song.bao.hua@hisilicon.com \
--cc=tabba@google.com \
--cc=tyhicks@linux.microsoft.com \
/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).