[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aWc-rA2nAwUH3uWD@zeus>
Date: Wed, 14 Jan 2026 15:58:52 +0900
From: Ryosuke Yasuoka <ryasuoka@...hat.com>
To: tglx@...utronix.de, mingo@...hat.com, bp@...en8.de,
dave.hansen@...ux.intel.com, hpa@...or.com
Cc: x86@...nel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] x86/traps: Print unhashed pointers on stack overflow
On Wed, Dec 24, 2025 at 04:07:32PM +0900, Ryosuke Yasuoka wrote:
> When a stack overflow occurs, the kernel prints hashed fault address and
> the stack range using %p. The actual addresses are required for
> debugging and hashed pointers provide no useful information in this
> context.
>
> Use %px to print the unhashed, raw addresses.
>
> Signed-off-by: Ryosuke Yasuoka <ryasuoka@...hat.com>
> ---
> arch/x86/kernel/traps.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/x86/kernel/traps.c b/arch/x86/kernel/traps.c
> index bcf1dedc1d00..5a6a772e0a6c 100644
> --- a/arch/x86/kernel/traps.c
> +++ b/arch/x86/kernel/traps.c
> @@ -549,7 +549,7 @@ __visible void __noreturn handle_stack_overflow(struct pt_regs *regs,
> {
> const char *name = stack_type_name(info->type);
>
> - printk(KERN_EMERG "BUG: %s stack guard page was hit at %p (stack is %p..%p)\n",
> + printk(KERN_EMERG "BUG: %s stack guard page was hit at %px (stack is %px..%px)\n",
> name, (void *)fault_address, info->begin, info->end);
>
> die("stack guard page", regs, 0);
>
> base-commit: b927546677c876e26eba308550207c2ddf812a43
> --
> 2.52.0
>
Hi all,
It's just a gentle ping on this patch.
Please let me know if there are any changes required. Any feedbacks are
welcome.
Thank you
Ryosuke
Powered by blists - more mailing lists