From: Andi Kleen <ak@suse.de>
To: Oliver Neukum <Oliver.Neukum@lrz.uni-muenchen.de>
Cc: Keith Owens <kaos@ocs.com.au>,
Andreas Dilger <adilger@turbolinux.com>, Andi Kleen <ak@suse.de>,
linux-kernel@vger.kernel.org
Subject: Re: [CHECKER] large stack variables (>=1K) in 2.4.4 and 2.4.4-ac8
Date: Fri, 25 May 2001 16:07:29 +0200 [thread overview]
Message-ID: <20010525160729.B32273@gruyere.muc.suse.de> (raw)
In-Reply-To: <24688.990773627@kao2.melbourne.sgi.com> <01052516035700.01561@idun>
In-Reply-To: <01052516035700.01561@idun>; from Oliver.Neukum@lrz.uni-muenchen.de on Fri, May 25, 2001 at 04:03:57PM +0200
On Fri, May 25, 2001 at 04:03:57PM +0200, Oliver Neukum wrote:
> > A small overflow of the kernel stack overwrites the struct task at the
> > bottom of the stack, recovery is dubious at best because we rely on
> > data in struct task. A large overflow of the kernel stack either
> > corrupts the storage below this task's stack, which could hit anything,
> > or it gets a stack fault.
>
> Is there a reason for the task structure to be at the bottom rather than the
> top of these two pages ?
This way you save one addition for every current access; which adds to
quite a few KB over the complete kernel.
-Andi
next prev parent reply other threads:[~2001-05-25 14:09 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-24 21:10 Dawson Engler
2001-05-24 22:40 ` Anton Altaparmakov
2001-05-24 23:08 ` Andreas Dilger
2001-05-24 23:33 ` Andi Kleen
2001-05-25 5:20 ` Keith Owens
2001-05-25 6:33 ` Andreas Dilger
2001-05-25 6:53 ` Keith Owens
2001-05-25 8:20 ` Andi Kleen
2001-05-25 8:31 ` Keith Owens
2001-05-25 8:39 ` Andi Kleen
2001-05-25 14:03 ` Oliver Neukum
2001-05-25 14:07 ` Andi Kleen [this message]
2001-05-25 15:45 ` dean gaudet
2001-05-25 16:34 ` Jonathan Lundell
2001-05-25 18:37 ` dean gaudet
2001-05-25 17:49 ` Jeff Dike
2001-05-25 7:11 ` David Welch
2001-05-25 8:08 ` Keith Owens
2001-05-25 15:31 ` dean gaudet
2001-05-25 15:49 ` Keith Owens
2001-05-25 18:46 ` dean gaudet
2001-05-25 8:14 ` Andi Kleen
2001-05-25 8:25 ` Keith Owens
2001-05-25 8:27 ` Andi Kleen
2001-05-25 8:37 ` Keith Owens
2001-05-25 8:17 ` Andi Kleen
2001-05-25 11:52 ` Brian Gerst
2001-05-25 11:53 ` Andi Kleen
2001-05-25 12:07 ` Brian Gerst
2001-05-25 3:38 ` Andrew Morton
2001-05-24 23:01 Mikael Pettersson
2001-05-25 2:48 ` Dawson Engler
2001-05-25 3:00 ` Alexander Viro
2001-05-25 3:07 ` Dawson Engler
2001-05-25 4:23 Dunlap, Randy
2001-07-03 9:15 VDA
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=20010525160729.B32273@gruyere.muc.suse.de \
--to=ak@suse.de \
--cc=Oliver.Neukum@lrz.uni-muenchen.de \
--cc=adilger@turbolinux.com \
--cc=kaos@ocs.com.au \
--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
all inboxes | Powered by JetHome®