All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ryosuke Yasuoka <ryasuoka@redhat.com>
To: tglx@linutronix.de, mingo@redhat.com, bp@alien8.de,
	dave.hansen@linux.intel.com, hpa@zytor.com
Cc: x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86/traps: Print unhashed pointers on stack overflow
Date: Wed, 14 Jan 2026 15:58:52 +0900	[thread overview]
Message-ID: <aWc-rA2nAwUH3uWD@zeus> (raw)
In-Reply-To: <20251224070735.454816-1-ryasuoka@redhat.com>

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@redhat.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


  reply	other threads:[~2026-01-14  6:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-24  7:07 [PATCH] x86/traps: Print unhashed pointers on stack overflow Ryosuke Yasuoka
2026-01-14  6:58 ` Ryosuke Yasuoka [this message]
2026-01-14 16:16 ` [tip: x86/misc] " tip-bot2 for Ryosuke Yasuoka

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=aWc-rA2nAwUH3uWD@zeus \
    --to=ryasuoka@redhat.com \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=x86@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.