From: Mark Rutland <mark.rutland@arm.com>
To: Maria Yu <quic_aiquny@quicinc.com>
Cc: catalin.marinas@arm.com, will@kernel.org, arnd@arndb.de,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, kernel@quicinc.com,
linux-arm-msm@vger.kernel.org, ardb@kernel.org
Subject: Re: [PATCH v2] arm64: module: PLT allowed even !RANDOM_BASE
Date: Tue, 24 Oct 2023 11:13:47 +0100 [thread overview]
Message-ID: <ZTeY0oBH3P22yOqA@FVFF77S0Q05N> (raw)
In-Reply-To: <20231024010954.6768-1-quic_aiquny@quicinc.com>
On Tue, Oct 24, 2023 at 09:09:54AM +0800, Maria Yu wrote:
> Module PLT feature can be enabled even when RANDOM_BASE is disabled.
> Break BLT entry counts of relocation types will make module plt entry
> allocation fail and finally exec format error for even correct and plt
> allocation available modules.
The patch itself looks good; it would be better if we could make the commit
message explicit that this is a fix. Could we please replace that with:
| arm64: module: fix PLT counting when CONFIG_RANDOMIZE_BASE=n
|
| The counting of module PLTs has been broken when CONFIG_RANDOMIZE_BASE=n
| since commit:
|
| 3e35d303ab7d22c4 ("arm64: module: rework module VA range selection")
|
| Prior to that commit, when CONFIG_RANDOMIZE_BASE=n, the kernel image and
| all modules were placed within a 128M region, and no PLTs were necessary
| for B or BL. Hence count_plts() and partition_branch_plt_relas() skipped
| handling B and BL when CONFIG_RANDOMIZE_BASE=n.
|
| After that commit, modules can be placed anywhere within a 2G window
| regardless of CONFIG_RANDOMIZE_BASE, and hence PLTs may be necessary for
| B and BL even when CONFIG_RANDOMIZE_BASE=n. Unfortunately that commit
| failed to update count_plts() and partition_branch_plt_relas()
| accordingly.
|
| Due to this, module_emit_plt_entry() may fail if an insufficient number
| of PLT entries have been reserved, resulting in modules failing to load
| with -ENOEXEC.
|
| Fix this by counting PLTs regardless of CONFIG_RANDOMIZE_BASE in
| count_plts() and partition_branch_plt_relas().
... and add a fixes tag:
Fixes: 3e35d303ab7d22c4 ("arm64: module: rework module VA range selection")
With that:
Reviewed-by: Mark Rutland <mark.rutland@arm.com>
Mark.
>
> Signed-off-by: Maria Yu <quic_aiquny@quicinc.com>
> ---
> arch/arm64/kernel/module-plts.c | 6 ------
> 1 file changed, 6 deletions(-)
>
> diff --git a/arch/arm64/kernel/module-plts.c b/arch/arm64/kernel/module-plts.c
> index bd69a4e7cd60..79200f21e123 100644
> --- a/arch/arm64/kernel/module-plts.c
> +++ b/arch/arm64/kernel/module-plts.c
> @@ -167,9 +167,6 @@ static unsigned int count_plts(Elf64_Sym *syms, Elf64_Rela *rela, int num,
> switch (ELF64_R_TYPE(rela[i].r_info)) {
> case R_AARCH64_JUMP26:
> case R_AARCH64_CALL26:
> - if (!IS_ENABLED(CONFIG_RANDOMIZE_BASE))
> - break;
> -
> /*
> * We only have to consider branch targets that resolve
> * to symbols that are defined in a different section.
> @@ -269,9 +266,6 @@ static int partition_branch_plt_relas(Elf64_Sym *syms, Elf64_Rela *rela,
> {
> int i = 0, j = numrels - 1;
>
> - if (!IS_ENABLED(CONFIG_RANDOMIZE_BASE))
> - return 0;
> -
> while (i < j) {
> if (branch_rela_needs_plt(syms, &rela[i], dstidx))
> i++;
>
> base-commit: 05d3ef8bba77c1b5f98d941d8b2d4aeab8118ef1
> --
> 2.17.1
>
_______________________________________________
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:[~2023-10-24 10:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-24 1:09 [PATCH v2] arm64: module: PLT allowed even !RANDOM_BASE Maria Yu
2023-10-24 8:25 ` Ard Biesheuvel
2023-10-24 10:13 ` Mark Rutland [this message]
2023-10-24 16:30 ` Catalin Marinas
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=ZTeY0oBH3P22yOqA@FVFF77S0Q05N \
--to=mark.rutland@arm.com \
--cc=ardb@kernel.org \
--cc=arnd@arndb.de \
--cc=catalin.marinas@arm.com \
--cc=kernel@quicinc.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_aiquny@quicinc.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