From: Jeff Dike <jdike@karaya.com>
To: dean gaudet <dean-list-linux-kernel@arctic.org>
Cc: linux-kernel@vger.kernel.org,
Jonathan Lundell <jlundell@pobox.com>, Andi Kleen <ak@suse.de>,
Oliver Neukum <Oliver.Neukum@lrz.uni-muenchen.de>,
Keith Owens <kaos@ocs.com.au>,
Andreas Dilger <adilger@turbolinux.com>
Subject: Re: [CHECKER] large stack variables (>=1K) in 2.4.4 and 2.4.4-ac8
Date: Fri, 25 May 2001 13:49:57 -0400 [thread overview]
Message-ID: <200105251749.NAA01282@karaya.com> (raw)
In-Reply-To: Your message of "Fri, 25 May 2001 11:37:48 PDT." <Pine.LNX.4.33.0105251130040.17081-100000@twinlark.arctic.org>
dean-list-linux-kernel@arctic.org said:
> also you don't need the task struct at the top to do this -- you just
> allocate 16k instead of 8k, put the task struct on page 0 of the
> allocation, unmap page 1, and put the stack frame on pages 2 and 3.
> (you'd probably have to do a 16k allocation regardless to get the
> guard page.)
This is exactly what UML does. My stacks are larger than the host's stacks
and I was having stack overflow problems when the Linux started saving SSE
state on signal frames.
So I doubled the stack size and put in a guard page while I was at it.
Jeff
next prev parent reply other threads:[~2001-05-25 18:49 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-24 21:10 [CHECKER] large stack variables (>=1K) in 2.4.4 and 2.4.4-ac8 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
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 [this message]
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
-- strict thread matches above, loose matches on Subject: below --
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=200105251749.NAA01282@karaya.com \
--to=jdike@karaya.com \
--cc=Oliver.Neukum@lrz.uni-muenchen.de \
--cc=adilger@turbolinux.com \
--cc=ak@suse.de \
--cc=dean-list-linux-kernel@arctic.org \
--cc=jlundell@pobox.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.