From: Eric Sandeen <sandeen@redhat.com>
To: linux-kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: [RFC][PATCH] detect & print stack overruns at oops time
Date: Fri, 31 Aug 2007 00:28:58 -0500 [thread overview]
Message-ID: <46D7A71A.7050800@redhat.com> (raw)
In thinking about the 4KSTACKS + STACKOVERFLOW problems, I thought
about this - if an oops occurs, explicitly print whether the current
esp is now overrunning the stack, whether the thread has ever overrun
the stack, else print the max stack excursion for the oopsing thread,
if DEBUG_STACK_USAGE is enabled.
1) maybe printing the info for a non-blown stack is not useful..
2) current esp past end of stack can already be deduced, but this
makes it more plain...
3) if the initialization of end_of_stack is problematic for
any reason, it could be removed and the "did we ever overrun"
test could be moved under the DEBUG_STACK_USAGE ifdef
Thoughts? This is a separate problem from the piggy dump_stack()
path, but it seems to me it might be useful in looking at stack-related
oopses when they do occur. With this change, it seems feasible
to turn off DEBUG_STACKOVERFLOW, turn on DEBUG_STACK_USAGE, and just
get the bad news when it's actually happened. :)
Thanks,
-Eric
Signed-off-by: Eric Sandeen <sandeen@redhat.com>
Index: linux-2.6.22-rc4/arch/i386/mm/fault.c
===================================================================
--- linux-2.6.22-rc4.orig/arch/i386/mm/fault.c
+++ linux-2.6.22-rc4/arch/i386/mm/fault.c
@@ -525,6 +525,8 @@ no_context:
if (oops_may_print()) {
__typeof__(pte_val(__pte(0))) page;
+ unsigned long *stackend = end_of_stack(tsk);
+ int overrun;
#ifdef CONFIG_X86_PAE
if (error_code & 16) {
@@ -543,6 +545,27 @@ no_context:
printk(KERN_ALERT "BUG: unable to handle kernel paging"
" request");
printk(" at virtual address %08lx\n",address);
+
+ overrun = (unsigned long)stackend - (unsigned long)(®s->esp);
+ if (overrun > 0) {
+ printk(KERN_ALERT "Thread overrunning stack by %d "
+ "bytes\n", overrun);
+ } else {
+#ifdef CONFIG_DEBUG_STACK_USAGE
+ int free;
+ unsigned long *n = stackend;
+ while (!*n)
+ n++;
+ free = (unsigned long)n - (unsigned long)stackend;
+ if (free)
+ printk(KERN_ALERT "Thread used within %d bytes"
+ " of stack end\n", free);
+#endif
+ /* won't catch 100% - stack may have 0s here by chance */
+ if (*stackend) /* was init'd to 0 */
+ printk(KERN_ALERT "Thread overran the stack?\n");
+ }
+
printk(KERN_ALERT " printing eip:\n");
printk("%08lx\n", regs->eip);
Index: linux-2.6.22-rc4/kernel/fork.c
===================================================================
--- linux-2.6.22-rc4.orig/kernel/fork.c
+++ linux-2.6.22-rc4/kernel/fork.c
@@ -163,6 +163,7 @@ static struct task_struct *dup_task_stru
{
struct task_struct *tsk;
struct thread_info *ti;
+ unsigned long *stackend;
prepare_to_copy(orig);
@@ -179,6 +180,8 @@ static struct task_struct *dup_task_stru
*tsk = *orig;
tsk->stack = ti;
setup_thread_stack(tsk, orig);
+ stackend = end_of_stack(tsk);
+ *stackend = 0; /* for overflow detection */
#ifdef CONFIG_CC_STACKPROTECTOR
tsk->stack_canary = get_random_int();
next reply other threads:[~2007-08-31 5:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-31 5:28 Eric Sandeen [this message]
2007-08-31 16:32 ` [RFC][PATCH] detect & print stack overruns at oops time Randy Dunlap
2007-08-31 16:36 ` Eric Sandeen
2007-09-05 9:30 ` Jarek Poplawski
2007-09-05 12:51 ` Eric Sandeen
2007-09-05 14:19 ` Jarek Poplawski
2007-09-05 14:29 ` Jarek Poplawski
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=46D7A71A.7050800@redhat.com \
--to=sandeen@redhat.com \
--cc=linux-kernel@vger.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