mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "tip-bot2 for Ryosuke Yasuoka" <tip-bot2@linutronix.de>
To: linux-tip-commits@vger.kernel.org
Cc: Ryosuke Yasuoka <ryasuoka@redhat.com>,
	"Borislav Petkov (AMD)" <bp@alien8.de>,
	x86@kernel.org, linux-kernel@vger.kernel.org
Subject: [tip: x86/misc] x86/traps: Print unhashed pointers on stack overflow
Date: Wed, 14 Jan 2026 16:16:59 -0000	[thread overview]
Message-ID: <176840741930.510.13867270177839334217.tip-bot2@tip-bot2> (raw)
In-Reply-To: <20251224070735.454816-1-ryasuoka@redhat.com>

The following commit has been merged into the x86/misc branch of tip:

Commit-ID:     6b32c93560cb194e10279bd3be3c1d0fa30df3e7
Gitweb:        https://git.kernel.org/tip/6b32c93560cb194e10279bd3be3c1d0fa30df3e7
Author:        Ryosuke Yasuoka <ryasuoka@redhat.com>
AuthorDate:    Wed, 24 Dec 2025 16:07:32 +09:00
Committer:     Borislav Petkov (AMD) <bp@alien8.de>
CommitterDate: Wed, 14 Jan 2026 16:31:53 +01:00

x86/traps: Print unhashed pointers on stack overflow

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>
Signed-off-by: Borislav Petkov (AMD) <bp@alien8.de>
Link: https://patch.msgid.link/20251224070735.454816-1-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 bcf1ded..5a6a772 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);

      parent reply	other threads:[~2026-01-14 16:17 UTC|newest]

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

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=176840741930.510.13867270177839334217.tip-bot2@tip-bot2 \
    --to=tip-bot2@linutronix.de \
    --cc=bp@alien8.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tip-commits@vger.kernel.org \
    --cc=ryasuoka@redhat.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®