mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Neil Horman <nhorman@tuxdriver.com>
To: nazim khan <naz_taurus@yahoo.com>
Cc: Michal Schmidt <xschmi00@stud.feec.vutbr.cz>,
	linux-kernel@vger.kernel.org
Subject: Re: How to find out kernel stack over flow?
Date: Thu, 8 Sep 2005 08:24:10 -0400	[thread overview]
Message-ID: <20050908122410.GA17189@hmsreliant.homelinux.net> (raw)
In-Reply-To: <20050908051716.94223.qmail@web52601.mail.yahoo.com>

On Wed, Sep 07, 2005 at 10:17:16PM -0700, nazim khan wrote:
> Thanks Michal for your response,
> 
> I forgot to mention that I am using linux 2.4.26,
> and STACKOVERFLOW option is not available here.
> 
> regards,
> Nazim
> 
It shouldn't be a difficult thing to hand-edit in (or at least an approximation
thereof).  Its really just a comparison of the current stack pointer in relation
to the current task_struct preformed in the do_IRQ function (so that it check
stack depth on interrupts).

Alternative to this method, or the netdump method I mentioned earlier.  If you
have some idea of which function(s) you are likely to be executing when the
stack overflows, you can also use -finstrument-functions as a finer grained
approach to detecting the problem.

Regards
Neil

> --- Michal Schmidt <xschmi00@stud.feec.vutbr.cz>
> wrote:
> 
> > nazim khan wrote:
> > > I suspect that one of my module that I am
> > inserting in
> > > the kernel may be causing the stack overflow which
> > is
> > > leading to kernel crash (may because it is
> > corrupting
> > > some one lese memory).
> > > 
> > > How can I find this out?
> > 
> > You could enable CONFIG_DEBUG_STACKOVERFLOW.
> > If you showed us your module's source code, someone
> > might see the bug.
> > 
> > Michal
> > 
> 
> 
> 
> 	
> 		
> ______________________________________________________
> Click here to donate to the Hurricane Katrina relief effort.
> http://store.yahoo.com/redcross-donate3/
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

-- 
/***************************************************
 *Neil Horman
 *Software Engineer
 *gpg keyid: 1024D / 0x92A74FA1 - http://pgp.mit.edu
 ***************************************************/

      reply	other threads:[~2005-09-08 12:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-07  7:28 nazim khan
2005-09-07  8:18 ` Michal Schmidt
2005-09-07 11:40   ` Neil Horman
2005-09-08  5:17   ` nazim khan
2005-09-08 12:24     ` Neil Horman [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=20050908122410.GA17189@hmsreliant.homelinux.net \
    --to=nhorman@tuxdriver.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=naz_taurus@yahoo.com \
    --cc=xschmi00@stud.feec.vutbr.cz \
    /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®