public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: jia zhang <jia.zhang2008@gmail.com>
Cc: linux-kernel@vger.kernel.org, tglx@linutronix.de, hpa@zytor.com,
	Arjan van de Ven <arjan@infradead.org>,
	Alexander van Heukelum <heukelum@mailshack.com>
Subject: [PATCH] x86: clean up stack overflow debug check
Date: Sun, 23 Nov 2008 09:08:16 +0100	[thread overview]
Message-ID: <20081123080816.GA30453@elte.hu> (raw)
In-Reply-To: <4928B72D.20901@gmail.com>


* jia zhang <jia.zhang2008@gmail.com> wrote:

> stack_overflow_check() should consider the stack usage of pt_regs, 
> and thus it could warn us in advance. Additionally, it looks a bit 
> good that the warning time starts at INITIAL_JIFFIES.
> 
> Signed-off-by: jia zhang <jia.zhang2008@gmail.com>
> ---
> Assume at the moment rsp get close to the check point before 
> interrupt arrives. When interrupt really happens, thread_info will 
> be partly overrode.
> 
>  arch/x86/kernel/irq_64.c |    7 ++++---
>  1 file changed, 4 insertions(+), 3 deletions(-)
> 
> --- a/arch/x86/kernel/irq_64.c
> +++ b/arch/x86/kernel/irq_64.c
> @@ -29,11 +29,12 @@
>  static inline void stack_overflow_check(struct pt_regs *regs)
>  {
>  	u64 curbase = (u64)task_stack_page(current);
> -	static unsigned long warned = -60*HZ;
> +	static unsigned long warned = INITIAL_JIFFIES - 60*HZ;
>  
>  	if (regs->sp >= curbase && regs->sp <= curbase + THREAD_SIZE &&
> -	    regs->sp <  curbase + sizeof(struct thread_info) + 128 &&
> -	    time_after(jiffies, warned + 60*HZ)) {
> +			regs->sp < curbase + sizeof(struct thread_info) +
> +			sizeof(struct pt_regs) + 128 &&
> +			time_after(jiffies, warned + 60*HZ)) {
>  		printk("do_IRQ: %s near stack overflow (cur:%Lx,sp:%lx)\n",
>  		       current->comm, curbase, regs->sp);
>  		show_stack(NULL,NULL);

applied to tip/x86/debug, thanks! I also applied the clean up patch 
below on top of your fix.

	Ingo

----------------->
>From f377fa123d0ec621e8e361ecc3f2a8ee70e81a2e Mon Sep 17 00:00:00 2001
From: Ingo Molnar <mingo@elte.hu>
Date: Sun, 23 Nov 2008 09:02:26 +0100
Subject: [PATCH] x86: clean up stack overflow debug check

Impact: cleanup

Simplify the irq-sampled stack overflow debug check:

 - eliminate an #idef

 - use WARN_ONCE() to emit a single warning (all bets are off
   after the first such warning anyway)

Signed-off-by: Ingo Molnar <mingo@elte.hu>
---
 arch/x86/kernel/irq_64.c |   25 ++++++++++---------------
 1 files changed, 10 insertions(+), 15 deletions(-)

diff --git a/arch/x86/kernel/irq_64.c b/arch/x86/kernel/irq_64.c
index b842fc8..1d3d0e7 100644
--- a/arch/x86/kernel/irq_64.c
+++ b/arch/x86/kernel/irq_64.c
@@ -18,7 +18,6 @@
 #include <asm/idle.h>
 #include <asm/smp.h>
 
-#ifdef CONFIG_DEBUG_STACKOVERFLOW
 /*
  * Probabilistic stack overflow check:
  *
@@ -28,20 +27,18 @@
  */
 static inline void stack_overflow_check(struct pt_regs *regs)
 {
+#ifdef CONFIG_DEBUG_STACKOVERFLOW
 	u64 curbase = (u64)task_stack_page(current);
-	static unsigned long warned = INITIAL_JIFFIES - 60*HZ;
-
-	if (regs->sp >= curbase && regs->sp <= curbase + THREAD_SIZE &&
-			regs->sp < curbase + sizeof(struct thread_info) +
-			sizeof(struct pt_regs) + 128 &&
-			time_after(jiffies, warned + 60*HZ)) {
-		printk("do_IRQ: %s near stack overflow (cur:%Lx,sp:%lx)\n",
-		       current->comm, curbase, regs->sp);
-		show_stack(NULL,NULL);
-		warned = jiffies;
-	}
-}
+
+	WARN_ONCE(regs->sp >= curbase &&
+		  regs->sp <= curbase + THREAD_SIZE &&
+		  regs->sp <  curbase + sizeof(struct thread_info) +
+					sizeof(struct pt_regs) + 128,
+
+		  "do_IRQ: %s near stack overflow (cur:%Lx,sp:%lx)\n",
+			current->comm, curbase, regs->sp);
 #endif
+}
 
 /*
  * do_IRQ handles all normal device IRQ's (the special
@@ -61,9 +58,7 @@ asmlinkage unsigned int do_IRQ(struct pt_regs *regs)
 	irq_enter();
 	irq = __get_cpu_var(vector_irq)[vector];
 
-#ifdef CONFIG_DEBUG_STACKOVERFLOW
 	stack_overflow_check(regs);
-#endif
 
 	desc = irq_to_desc(irq);
 	if (likely(desc))

      reply	other threads:[~2008-11-23  8:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-23  1:51 [PATCH] x86_64: fix the check point in stack_overflow_check jia zhang
2008-11-23  8:08 ` Ingo Molnar [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=20081123080816.GA30453@elte.hu \
    --to=mingo@elte.hu \
    --cc=arjan@infradead.org \
    --cc=heukelum@mailshack.com \
    --cc=hpa@zytor.com \
    --cc=jia.zhang2008@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglx@linutronix.de \
    /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