All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Lutomirski <luto@kernel.org>
To: X86 ML <x86@kernel.org>
Cc: Borislav Petkov <bpetkov@suse.de>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Brian Gerst <brgerst@gmail.com>,
	Dave Hansen <dave.hansen@intel.com>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Josh Poimboeuf <jpoimboe@redhat.com>,
	Andy Lutomirski <luto@kernel.org>
Subject: [PATCH 15/16] x86/irq/64: In the stack overflow warning, print the offending IP
Date: Mon, 20 Nov 2017 09:07:46 -0800	[thread overview]
Message-ID: <0805aec810b8eb17f03b0ba63e4b916c8a0aba27.1511195781.git.luto@kernel.org> (raw)
In-Reply-To: <cover.1511195781.git.luto@kernel.org>
In-Reply-To: <cover.1511195781.git.luto@kernel.org>

In case something goes wrong with unwind (not unlikely in case of
overflow), print the offending IP where we detected the overflow.
---
 arch/x86/kernel/irq_64.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/arch/x86/kernel/irq_64.c b/arch/x86/kernel/irq_64.c
index 020efbf5786b..d86e344f5b3d 100644
--- a/arch/x86/kernel/irq_64.c
+++ b/arch/x86/kernel/irq_64.c
@@ -57,10 +57,10 @@ static inline void stack_overflow_check(struct pt_regs *regs)
 	if (regs->sp >= estack_top && regs->sp <= estack_bottom)
 		return;
 
-	WARN_ONCE(1, "do_IRQ(): %s has overflown the kernel stack (cur:%Lx,sp:%lx,irq stk top-bottom:%Lx-%Lx,exception stk top-bottom:%Lx-%Lx)\n",
+	WARN_ONCE(1, "do_IRQ(): %s has overflown the kernel stack (cur:%Lx,sp:%lx,irq stk top-bottom:%Lx-%Lx,exception stk top-bottom:%Lx-%Lx,ip:%pF)\n",
 		current->comm, curbase, regs->sp,
 		irq_stack_top, irq_stack_bottom,
-		estack_top, estack_bottom);
+		estack_top, estack_bottom, (void *)regs->ip);
 
 	if (sysctl_panic_on_stackoverflow)
 		panic("low stack detected by irq handler - check messages\n");
-- 
2.13.6

  parent reply	other threads:[~2017-11-20 17:08 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-20 17:07 [PATCH 00/16] Entry stuff, in decent shape now Andy Lutomirski
2017-11-20 17:07 ` [PATCH 01/16] x86/asm/64: Allocate and enable the SYSENTER stack Andy Lutomirski
2017-11-20 21:55   ` Thomas Gleixner
2017-11-21 10:47   ` Borislav Petkov
2017-11-20 17:07 ` [PATCH 02/16] x86/dumpstack: Add get_stack_info() support for " Andy Lutomirski
2017-11-20 20:42   ` Josh Poimboeuf
2017-11-20 20:46     ` Andy Lutomirski
2017-11-20 21:00       ` Josh Poimboeuf
2017-11-20 21:07         ` Andy Lutomirski
2017-11-20 21:27           ` Josh Poimboeuf
2017-11-20 21:30             ` Andy Lutomirski
2017-11-20 21:55               ` Josh Poimboeuf
2017-11-21  1:39                 ` Andy Lutomirski
2017-11-21  2:29                   ` Josh Poimboeuf
2017-11-20 17:07 ` [PATCH 03/16] x86/gdt: Put per-cpu GDT remaps in ascending order Andy Lutomirski
2017-11-20 21:56   ` Thomas Gleixner
2017-11-21 17:16   ` Borislav Petkov
2017-11-20 17:07 ` [PATCH 04/16] x86/fixmap: Generalize the GDT fixmap mechanism Andy Lutomirski
2017-11-20 22:01   ` Thomas Gleixner
2017-11-21  1:21     ` Andy Lutomirski
2017-11-21  8:29       ` Thomas Gleixner
2017-11-20 17:07 ` [PATCH 05/16] x86/asm: Fix assumptions that the HW TSS is at the beginning of cpu_tss Andy Lutomirski
2017-11-20 22:22   ` Thomas Gleixner
2017-11-20 17:07 ` [PATCH 06/16] x86/dumpstack: Handle stack overflow on all stacks Andy Lutomirski
2017-11-20 17:07 ` [PATCH 07/16] x86/asm: Move SYSENTER_stack to the beginning of struct tss_struct Andy Lutomirski
2017-11-20 23:37   ` Thomas Gleixner
2017-11-21  1:25     ` Andy Lutomirski
2017-11-20 17:07 ` [PATCH 08/16] x86/asm: Remap the TSS into the cpu entry area Andy Lutomirski
2017-11-20 17:07 ` [PATCH 09/16] x86/asm/64: Separate cpu_current_top_of_stack from TSS.sp0 Andy Lutomirski
2017-11-20 17:07 ` [PATCH 10/16] x86/espfix/64: Stop assuming that pt_regs is on the entry stack Andy Lutomirski
2017-11-20 17:07 ` [PATCH 11/16] x86/asm/64: Use a percpu trampoline stack for IDT entries Andy Lutomirski
2017-11-21  7:20   ` Ingo Molnar
2017-11-21 15:36     ` Andy Lutomirski
2017-11-21 18:57   ` Dave Hansen
2017-11-22  3:45     ` Andy Lutomirski
2017-11-20 17:07 ` [PATCH 12/16] x86/asm/64: Return to userspace from the trampoline stack Andy Lutomirski
2017-11-20 17:07 ` [PATCH 13/16] x86/entry/64: Create a percpu SYSCALL entry trampoline Andy Lutomirski
2017-11-21  2:34   ` Josh Poimboeuf
2017-11-21  3:20     ` Andy Lutomirski
2017-11-20 17:07 ` [PATCH 14/16] x86/irq: Remove an old outdated comment about context tracking races Andy Lutomirski
2017-11-21  6:25   ` Ingo Molnar
2017-11-20 17:07 ` Andy Lutomirski [this message]
2017-11-21  6:26   ` [PATCH 15/16] x86/irq/64: In the stack overflow warning, print the offending IP Ingo Molnar
2017-11-20 17:07 ` [PATCH 16/16] x86/entry/64: Move the IST stacks into cpu_entry_area Andy Lutomirski
2017-11-21  7:38   ` Ingo Molnar
2017-11-21 14:45     ` Andrey Ryabinin
2017-11-23 15:25       ` Andy Lutomirski
2017-11-21 15:33     ` Andy Lutomirski
2017-11-20 18:48 ` [PATCH 00/16] Entry stuff, in decent shape now Andy Lutomirski
2017-11-21  7:33 ` Ingo Molnar
2017-11-21 15:59   ` Andy Lutomirski
2017-11-21 16:12     ` Andy Lutomirski

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=0805aec810b8eb17f03b0ba63e4b916c8a0aba27.1511195781.git.luto@kernel.org \
    --to=luto@kernel.org \
    --cc=bpetkov@suse.de \
    --cc=brgerst@gmail.com \
    --cc=dave.hansen@intel.com \
    --cc=jpoimboe@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --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.