Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Will Deacon <will@kernel.org>
To: Mark Brown <broonie@kernel.org>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] arm64: bti: Fix support for userspace only BTI
Date: Tue, 12 May 2020 11:39:09 +0100	[thread overview]
Message-ID: <20200512103908.GB3021@willie-the-truck> (raw)
In-Reply-To: <20200512092155.56931-1-broonie@kernel.org>

On Tue, May 12, 2020 at 10:21:55AM +0100, Mark Brown wrote:
> When setting PTE_MAYBE_GP we check system_supports_bti() but this is
> true for systems where only CONFIG_BTI is set causing us to enable BTI
> on some kernel text. Add an extra check for the kernel mode option,
> using an ifdef due to line length.
> 
> Fixes: c8027285e366 (arm64: Set GP bit in kernel page tables to enable BTI for the kernel)
> Signed-off-by: Mark Brown <broonie@kernel.org>
> ---
>  arch/arm64/include/asm/pgtable-prot.h | 4 ++++
>  1 file changed, 4 insertions(+)
> 
> diff --git a/arch/arm64/include/asm/pgtable-prot.h b/arch/arm64/include/asm/pgtable-prot.h
> index 310690332896..3f07a044bdfb 100644
> --- a/arch/arm64/include/asm/pgtable-prot.h
> +++ b/arch/arm64/include/asm/pgtable-prot.h
> @@ -32,7 +32,11 @@ extern bool arm64_use_ng_mappings;
>  #define PTE_MAYBE_NG		(arm64_use_ng_mappings ? PTE_NG : 0)
>  #define PMD_MAYBE_NG		(arm64_use_ng_mappings ? PMD_SECT_NG : 0)
>

Might be worth a comment here in case somebody tries to "clean this up"
later on!

> +#ifdef CONFIG_ARM64_BTI_KERNEL
>  #define PTE_MAYBE_GP		(system_supports_bti() ? PTE_GP : 0)
> +#else
> +#define PTE_MAYBE_GP		0
> +#endif

I also notice we have a funny check in the vdso code:

  if (IS_ENABLED(CONFIG_ARM64_BTI_KERNEL) && system_supports_bti())

but why do we care about CONFIG_ARM64_BTI_KERNEL for the vdso pages?

Will

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2020-05-12 10:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-12  9:21 [PATCH] arm64: bti: Fix support for userspace only BTI Mark Brown
2020-05-12 10:39 ` Will Deacon [this message]
2020-05-12 11:05   ` Mark Brown
2020-05-12 11:42     ` Will Deacon
2020-05-13 14:46     ` Dave Martin
2020-05-13 15:08       ` Mark Brown
2020-05-13 16:49         ` Dave Martin

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=20200512103908.GB3021@willie-the-truck \
    --to=will@kernel.org \
    --cc=broonie@kernel.org \
    --cc=catalin.marinas@arm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox