[PATCH v2 17/21] arm64: entry: Use SPSel to switch to overflow stack

Jinjie Ruan ruanjinjie at huawei.com
Thu Oct 8 04:59:19 PDT 2026



在 2026/9/19 0:14, Will Deacon 写道:
> When detecting a stack overflow on exception entry from EL1, use SPSel
> to switch to the overflow stack without corrupting any GPRs. Not only is
> this simpler than the previous logic, but it also opens the door to
> more complicated overflow checks (for example, based on per-task stack
> sizes or stacks which are not aligned to a specific page order) as well
> as the possibility of returning from a stack fault if we were able to
> resolve it.
> 
> Cc: Mark Rutland <mark.rutland at arm.com>
> Signed-off-by: Will Deacon <will at kernel.org>
> ---
>  arch/arm64/kernel/entry.S | 69 ++++++++++++---------------------------
>  1 file changed, 21 insertions(+), 48 deletions(-)
> 
> diff --git a/arch/arm64/kernel/entry.S b/arch/arm64/kernel/entry.S
> index 6958ee238649..b4df2f23ebe7 100644
> --- a/arch/arm64/kernel/entry.S
> +++ b/arch/arm64/kernel/entry.S
> @@ -51,11 +51,11 @@
>  	mov	x30, xzr
>  	.endif
>  .Lskip_tramp_vectors_cleanup\@:
> -	.endif
> -
> +	sub	sp, sp, #PT_REGS_SIZE
> +	.else	/* \el == 1 */
> +	.ifc	\ht, h
>  	sub	sp, sp, #PT_REGS_SIZE
>  
> -	.if	\el == 1
>  	/*
>  	 * Test whether the SP has overflowed, without corrupting a GPR.
>  	 * Task and IRQ stacks are aligned so that SP & (1 << THREAD_SHIFT)
> @@ -63,45 +63,16 @@
>  	 */
>  	add	sp, sp, x0			// sp' = sp + x0
>  	sub	x0, sp, x0			// x0' = sp' - x0 = (sp + x0) - x0 = sp
> -	tbnz	x0, #THREAD_SHIFT, 0f
> +	tbnz	x0, #THREAD_SHIFT, __bad_stack
>  	sub	x0, sp, x0			// x0'' = sp' - x0' = (sp + x0) - sp = x0
>  	sub	sp, sp, x0			// sp'' = sp' - x0 = (sp + x0) - x0 = sp
> +	.else	/* EL1t */
> +	msr	spsel, #0			// Stay on the overflow stack
> +	sub	sp, sp, #PT_REGS_SIZE
> +	.endif
>  	.endif
>  
>  	b	el\el\ht\()_\regsize\()_\label
> -
> -	.if	\el == 1
> -0:
> -	/*
> -	 * Either we've just detected an overflow, or we've taken an exception
> -	 * while on the overflow stack. Either way, we won't return to
> -	 * userspace, and can clobber EL0 registers to free up GPRs.
> -	 */
> -
> -	/* Stash the original SP (minus PT_REGS_SIZE) in tpidr_el0. */
> -	msr	tpidr_el0, x0
> -
> -	/* Recover the original x0 value and stash it in sp_el0 */
> -	sub	x0, sp, x0
> -	msr	sp_el0, x0
> -
> -	/* Switch to the overflow stack */
> -	adr_this_cpu sp, overflow_stack + OVERFLOW_STACK_SIZE, x0
> -
> -	/*
> -	 * Check whether we were already on the overflow stack. This may happen
> -	 * after panic() re-enables interrupts.
> -	 */
> -	mrs	x0, tpidr_el0			// sp of interrupted context
> -	sub	x0, sp, x0			// delta with top of overflow stack
> -	tst	x0, #~(OVERFLOW_STACK_SIZE - 1)	// within range?
> -	b.ne	__bad_stack			// no? -> bad stack pointer
> -
> -	/* We were already on the overflow stack. Restore sp/x0 and carry on. */
> -	sub	sp, sp, x0
> -	mrs	x0, sp_el0
> -	b	el\el\ht\()_\regsize\()_\label
> -	.endif
>  .org .Lventry_start\@ + 128	// Did we overflow the ventry slot?
>  	.endm
>  
> @@ -544,22 +515,24 @@ SYM_CODE_END(vectors)
>  
>  SYM_CODE_START_LOCAL(__bad_stack)
>  	/*
> -	 * We detected an overflow in kernel_ventry, which switched to the
> -	 * overflow stack. Stash the exception regs, and head to our overflow
> -	 * handler.
> +	 * We detected an overflow in kernel_ventry.
> +	 * Restore SP and X0.
>  	 */
> +	sub	x0, sp, x0
> +	sub	sp, sp, x0
> +	add	sp, sp, #PT_REGS_SIZE
>  
> -	/* Restore the original x0 value */
> -	mrs	x0, sp_el0
> +	/* Switch to the overflow stack */
> +	msr	spsel, #0
>  
> -	/*
> -	 * Store the original GPRs to the new stack. The orginal SP (minus
> -	 * PT_REGS_SIZE) was stashed in tpidr_el0 by kernel_ventry.
> -	 */
> +	/* Stash the exception regs */
>  	sub	sp, sp, #PT_REGS_SIZE
>  	kernel_entry 1
> -	mrs	x0, tpidr_el0
> -	add	x0, x0, #PT_REGS_SIZE
> +
> +	/* Fix-up the saved SP */
> +	msr	spsel, #1
> +	mov	x0, sp
> +	msr	spsel, #0

LGTM
Reviewed-by: Jinjie Ruan <ruanjinjie at huawei.com>

>  	str	x0, [sp, #S_SP]
>  
>  	/* Stash the regs for handle_bad_stack */

-- 
Best regards,
Jinjie




More information about the linux-arm-kernel mailing list