From: William Lee Irwin III <wli@holomorphy.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Breno <brenosp@brasilsec.com.br>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: stack overflow
Date: Fri, 12 Sep 2003 16:25:07 -0700 [thread overview]
Message-ID: <20030912232507.GV4306@holomorphy.com> (raw)
In-Reply-To: <1063408711.6740.4.camel@dhcp23.swansea.linux.org.uk>
On Sad, 2003-09-13 at 00:06, William Lee Irwin III wrote:
>> What he actually wants is in-kernel user stack overflow checking, which
>> is basically impossible since user stacks are demand paged. He's been
>> told this before and failed to absorb it.
On Sat, Sep 13, 2003 at 12:18:32AM +0100, Alan Cox wrote:
> We will fault and error on a user stack exceed. You need to use
> sigaltstack to catch it for obvious reasons. You can also use mmap and
> drop in red zones on user space stacks
Stack rlimits are fine and we already do those; the rest sounds like
something userspace has to do.
-- wli
next prev parent reply other threads:[~2003-09-12 23:26 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-12 17:53 stack overflow Breno
2003-09-12 22:50 ` Andreas Dilger
2003-09-12 19:14 ` Breno
2003-09-12 23:06 ` William Lee Irwin III
2003-09-12 19:23 ` Breno
2003-09-12 23:18 ` Alan Cox
2003-09-12 23:25 ` William Lee Irwin III [this message]
2003-09-12 23:18 ` stack overflow - kernel thread Breno
-- strict thread matches above, loose matches on Subject: below --
2004-03-22 17:40 stack overflow Stuart_Hayes-DYMqY+WieiM
2004-03-10 17:08 Stuart_Hayes-DYMqY+WieiM
[not found] ` <CE41BFEF2481C246A8DE0D2B4DBACF4F020E5FD9-novRXWwkcpil7xnNSM18fRtLTTO9Z+wMojBamW5iJbs@public.gmane.org>
2004-03-10 18:40 ` Len Brown
2004-03-10 15:56 Stuart_Hayes-DYMqY+WieiM
2004-03-09 22:48 Moore, Robert
2004-03-09 21:04 Stuart_Hayes-DYMqY+WieiM
2004-03-09 20:00 Stuart_Hayes-DYMqY+WieiM
2004-03-09 18:34 Moore, Robert
2004-03-08 16:43 Stuart_Hayes-DYMqY+WieiM
[not found] ` <CE41BFEF2481C246A8DE0D2B4DBACF4F128AA4-novRXWwkcpil7xnNSM18fRtLTTO9Z+wMojBamW5iJbs@public.gmane.org>
2004-03-08 18:26 ` Andi Kleen
[not found] ` <20040308182630.GB9490-B4tOwbsTzaBolqkO4TVVkw@public.gmane.org>
2004-03-09 7:17 ` Len Brown
2004-03-10 4:33 ` Len Brown
[not found] ` <1078893223.2346.585.camel-D2Zvc0uNKG8@public.gmane.org>
2004-03-10 13:32 ` Andi Kleen
[not found] ` <20040310133208.GC12272-B4tOwbsTzaBolqkO4TVVkw@public.gmane.org>
2004-03-10 18:44 ` Len Brown
2003-01-24 7:08 Stack overflow Madhavi
2003-01-24 7:53 ` Linux Geek
2003-01-24 15:32 ` GrandMasterLee
2003-01-24 15:41 ` Madhavi
2003-01-24 16:42 ` Richard B. Johnson
2003-01-24 16:52 ` Gianni Tedesco
2000-09-06 13:25 stack overflow Zeshan Ahmad
2000-09-05 19:03 Zeshan Ahmad
2000-09-06 8:33 ` Mark Hemment
2000-09-04 10:47 Zeshan Ahmad
2000-09-04 11:03 ` Matti Aarnio
2000-09-04 11:23 ` Tigran Aivazian
2000-09-05 10:55 ` Mark Hemment
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=20030912232507.GV4306@holomorphy.com \
--to=wli@holomorphy.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=brenosp@brasilsec.com.br \
--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.