Re: [RFC][PATCH] detect & print stack overruns at oops time

Randy Dunlap wrote:
> On Fri, 31 Aug 2007 00:28:58 -0500 Eric Sandeen wrote:
> 
>> 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
>> @@ -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)(&regs->esp);
>> +		if (overrun > 0) {
>> +			printk(KERN_ALERT "Thread overrunning stack by %d "
>> +							"bytes\n", overrun);
>> +		} else {
> 
> Hi,
> 
> Is there something that tells us what <Thread> is doing all of this
> bad juju?

Sure, the rest of the oops report will.

-Eric
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• References:
  • [RFC][PATCH] detect & print stack overruns at oops time
    • From: Eric Sandeen <[email protected]>
  • Re: [RFC][PATCH] detect & print stack overruns at oops time
    • From: Randy Dunlap <[email protected]>

• Prev by Date: Re: [PATCH] Increase lockdep MAX_LOCK_DEPTH
• Next by Date: Re: [11/36] Use page_cache_xxx in fs/buffer.c
• Previous by thread: Re: [RFC][PATCH] detect & print stack overruns at oops time
• Next by thread: Re: [RFC][PATCH] detect & print stack overruns at oops time
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]