Linux Trace Kernel
 help / color / mirror / Atom feed
From: Jeremy Linton <jeremy.linton@arm.com>
To: linux-trace-kernel@vger.kernel.org
Cc: linux-perf-users@vger.kernel.org, mhiramat@kernel.org,
	oleg@redhat.com, peterz@infradead.org, mingo@redhat.com,
	acme@kernel.org, namhyung@kernel.org, mark.rutland@arm.com,
	alexander.shishkin@linux.intel.com, jolsa@kernel.org,
	irogers@google.com, adrian.hunter@intel.com,
	kan.liang@linux.intel.com, thiago.bauermann@linaro.org,
	broonie@kernel.org, yury.khrustalev@arm.com,
	kristina.martsenko@arm.com, liaochang1@huawei.com,
	catalin.marinas@arm.com, will@kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v7 4/7] arm64: probes: Add GCS support to bl/blr/ret
Date: Thu, 18 Sep 2025 07:54:12 -0500	[thread overview]
Message-ID: <90c78c6d-2e73-44a6-b933-779477d15745@arm.com> (raw)
In-Reply-To: <20250825033421.463669-5-jeremy.linton@arm.com>

Hi,

On 8/24/25 10:34 PM, Jeremy Linton wrote:
> The arm64 probe simulation doesn't currently have logic in place
> to deal with GCS and this results in core dumps if probes are inserted
> at control flow locations. Fix-up bl, blr and ret to manipulate the
> shadow stack as needed.
> 
> While we manipulate and validate the shadow stack correctly, the
> hardware provides additional security by only allowing GCS operations
> against pages which are marked to support GCS. For writing there is
> gcssttr() which enforces this, but there isn't an equivalent for
> reading. This means that uprobe users should be aware that probing on
> control flow instructions which require reading the shadow stack (ex:
> ret) offers lower security guarantees than what is achieved without
> the uprobe active.
> 
> Signed-off-by: Jeremy Linton <jeremy.linton@arm.com>
> Reviewed-by: Catalin Marinas <catalin.marinas@arm.com>
> ---
>   arch/arm64/kernel/probes/simulate-insn.c | 44 +++++++++++++++++++-----
>   1 file changed, 35 insertions(+), 9 deletions(-)
> 
> diff --git a/arch/arm64/kernel/probes/simulate-insn.c b/arch/arm64/kernel/probes/simulate-insn.c
> index 09a0b36122d0..97ed4db75417 100644
> --- a/arch/arm64/kernel/probes/simulate-insn.c
> +++ b/arch/arm64/kernel/probes/simulate-insn.c
> @@ -13,6 +13,7 @@
>   #include <asm/traps.h>
>   
>   #include "simulate-insn.h"
> +#include "asm/gcs.h"
>   
>   #define bbl_displacement(insn)		\
>   	sign_extend32(((insn) & 0x3ffffff) << 2, 27)
> @@ -49,6 +50,21 @@ static inline u32 get_w_reg(struct pt_regs *regs, int reg)
>   	return lower_32_bits(pt_regs_read_reg(regs, reg));
>   }
>   
> +static inline int update_lr(struct pt_regs *regs, long addr)
> +{
> +	int err = 0;
> +
> +	if (user_mode(regs) && task_gcs_el0_enabled(current)) {
> +		push_user_gcs(addr, &err);
> +		if (err) {
> +			force_sig(SIGSEGV);
> +			return err;
> +		}
> +	}
> +	procedure_link_pointer_set(regs, addr);
> +	return err;
> +}
> +
>   static bool __kprobes check_cbz(u32 opcode, struct pt_regs *regs)
>   {
>   	int xn = opcode & 0x1f;
> @@ -107,9 +123,9 @@ simulate_b_bl(u32 opcode, long addr, struct pt_regs *regs)
>   {
>   	int disp = bbl_displacement(opcode);
>   
> -	/* Link register is x30 */
>   	if (opcode & (1 << 31))
> -		set_x_reg(regs, 30, addr + 4);
> +		if (update_lr(regs, addr + 4))
> +			return;
>   
>   	instruction_pointer_set(regs, addr + disp);
>   }
> @@ -129,21 +145,31 @@ void __kprobes
>   simulate_br_blr(u32 opcode, long addr, struct pt_regs *regs)
>   {
>   	int xn = (opcode >> 5) & 0x1f;
> +	int b_target = get_x_reg(regs, xn);

Ugh, I was staring at this set and realized that this type is wrong, it 
should be 'long'. I will send a patch once I sanity check it on 
something that isn't a model.


>   
> -	/* update pc first in case we're doing a "blr lr" */
> -	instruction_pointer_set(regs, get_x_reg(regs, xn));
> -
> -	/* Link register is x30 */
>   	if (((opcode >> 21) & 0x3) == 1)
> -		set_x_reg(regs, 30, addr + 4);
> +		if (update_lr(regs, addr + 4))
> +			return;
> +
> +	instruction_pointer_set(regs, b_target);
>   }
>   
>   void __kprobes
>   simulate_ret(u32 opcode, long addr, struct pt_regs *regs)
>   {
> +	u64 ret_addr;
> +	int err = 0;
>   	int xn = (opcode >> 5) & 0x1f;
> -
> -	instruction_pointer_set(regs, get_x_reg(regs, xn));
> +	unsigned long r_target = get_x_reg(regs, xn);
> +
> +	if (user_mode(regs) && task_gcs_el0_enabled(current)) {
> +		ret_addr = pop_user_gcs(&err);
> +		if (err || ret_addr != r_target) {
> +			force_sig(SIGSEGV);
> +			return;
> +		}
> +	}
> +	instruction_pointer_set(regs, r_target);
>   }
>   
>   void __kprobes


  reply	other threads:[~2025-09-18 12:54 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-25  3:34 [PATCH v7 0/7] arm64: Enable UPROBES with GCS Jeremy Linton
2025-08-25  3:34 ` [PATCH v7 1/7] arm64: probes: Break ret out from bl/blr Jeremy Linton
2025-08-25  3:34 ` [PATCH v7 2/7] arm64: uaccess: Move existing GCS accessors definitions to gcs.h Jeremy Linton
2025-08-25  3:34 ` [PATCH v7 3/7] arm64: uaccess: Add additional userspace GCS accessors Jeremy Linton
2025-08-25  3:34 ` [PATCH v7 4/7] arm64: probes: Add GCS support to bl/blr/ret Jeremy Linton
2025-09-18 12:54   ` Jeremy Linton [this message]
2025-09-18 13:56     ` Will Deacon
2025-08-25  3:34 ` [PATCH v7 5/7] arm64: uprobes: Add GCS support to uretprobes Jeremy Linton
2025-08-25  3:34 ` [PATCH v7 6/7] arm64: Kconfig: Remove GCS restrictions on UPROBES Jeremy Linton
2025-08-25  3:34 ` [PATCH v7 7/7] uprobes: uprobe_warn should use passed task Jeremy Linton
2025-09-16 21:13 ` [PATCH v7 0/7] arm64: Enable UPROBES with GCS Will Deacon

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=90c78c6d-2e73-44a6-b933-779477d15745@arm.com \
    --to=jeremy.linton@arm.com \
    --cc=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=broonie@kernel.org \
    --cc=catalin.marinas@arm.com \
    --cc=irogers@google.com \
    --cc=jolsa@kernel.org \
    --cc=kan.liang@linux.intel.com \
    --cc=kristina.martsenko@arm.com \
    --cc=liaochang1@huawei.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mhiramat@kernel.org \
    --cc=mingo@redhat.com \
    --cc=namhyung@kernel.org \
    --cc=oleg@redhat.com \
    --cc=peterz@infradead.org \
    --cc=thiago.bauermann@linaro.org \
    --cc=will@kernel.org \
    --cc=yury.khrustalev@arm.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