From: Andreas Dilger <adilger@clusterfs.com>
To: Dave Hansen <haveblue@us.ibm.com>
Cc: Linus Torvalds <torvalds@transmeta.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] (3/3) stack overflow checking for x86
Date: Fri, 18 Oct 2002 16:48:49 -0600 [thread overview]
Message-ID: <20021018224849.GS14989@clusterfs.com> (raw)
In-Reply-To: <3DB08BD4.50607@us.ibm.com>
On Oct 18, 2002 15:31 -0700, Dave Hansen wrote:
> Greg KH just pointed out that someone else snuck in an overflow check.
> However, they take completely different approaches. The Ben LaHaise
> one that I posted uses GCC features to check the stack on entry to all
> functions. The one in the tree now is much, much simpler than Ben's,
> but only works only for detecting problems at the time that an
> interrupt actually occurs.
Yes, we had that patch in the RH 2.4 kernel, but it didn't detect the
stack overflow we spent days to track. Our problem was just one of
a really deep stack: RPC-to-network-filesystem-on-ext3-with-htree.
This overflowed the 8kB stack even without an interrupt happening.
We fixed the htree and the network filesystem stack usage, but if we
added LVM/EVMS into the mix (which we would have in production) and
threw in a piggy interrupt handler we would possibly again overflow
an 8kB stack, so having a per-entry/exit stack checker would be great.
Cheers, Andreas
--
Andreas Dilger
http://www-mddsp.enel.ucalgary.ca/People/adilger/
http://sourceforge.net/projects/ext2resize/
next prev parent reply other threads:[~2002-10-18 22:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-18 22:07 [PATCH] (3/3) stack overflow checking for x86 Dave Hansen
2002-10-18 22:31 ` Dave Hansen
2002-10-18 22:48 ` Andreas Dilger [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-10-31 19:18 [PATCH] (1/3) cleanup thread info on x86 David C. Hansen
2002-10-31 19:20 ` [PATCH] (3/3) stack overflow checking for x86 David C. Hansen
2002-10-31 21:30 ` Dave Jones
2002-10-31 22:08 ` David C. Hansen
2002-11-01 12:59 ` Alan Cox
2002-11-01 13:42 ` Dave Jones
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=20021018224849.GS14989@clusterfs.com \
--to=adilger@clusterfs.com \
--cc=haveblue@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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