From: Andi Kleen <ak@muc.de>
To: Stas Sergeev <stsp@aknet.ru>
Cc: Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: Segfault on the i386 enter instruction
Date: 15 May 2006 20:44:01 +0200
Date: Mon, 15 May 2006 20:44:01 +0200 [thread overview]
Message-ID: <20060515184401.GA89194@muc.de> (raw)
In-Reply-To: <4468B733.7010101@aknet.ru>
On Mon, May 15, 2006 at 09:15:31PM +0400, Stas Sergeev wrote:
> Hi.
>
> Andi Kleen wrote:
> >>Aren't the rlimit and the other checks of acct_stack_growth()
> >>not enough, or am I missing something obvious?
> >Traditionally Linux doesn't have a stack ulimit.
> That clarifies the roots of this %esp check, as without
> the stack ulimit and without the proper memory accounting
> (the case of 2.4?) such a check is the "last hope" - I've
> got the point. But are there the reasons to still keep it
> in 2.6, considering also the false-positives? It seems to
> have the STACK_RLIMIT and it seems to get the memory accounting
> right, and not too many arches seem to have such a check even.
Linux doesn't have a STACK_RLIMIT by default no.
It is set by a few distributions (for use with flexmmap) in PAM, but
not by all. The kernel defaults don't have it.
-Andi
next prev parent reply other threads:[~2006-05-15 18:44 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-14 17:56 Segfault on the i386 enter instruction Stas Sergeev
2006-05-15 7:40 ` Andi Kleen
2006-05-15 17:15 ` Stas Sergeev
2006-05-15 18:44 ` Andi Kleen [this message]
2006-05-15 19:38 ` Stas Sergeev
2006-05-15 19:56 ` Lee Revell
2006-05-15 22:49 ` Ingo Oeser
2006-05-15 22:56 ` Lee Revell
-- strict thread matches above, loose matches on Subject: below --
2006-05-17 8:20 Chuck Ebbert
2006-05-16 2:29 Chuck Ebbert
2006-05-16 9:32 ` Andi Kleen
2006-05-12 13:16 Tomasz Malesinski
2006-05-12 13:47 ` Denis Vlasenko
2006-05-12 13:50 ` Andi Kleen
2006-05-12 14:03 ` Denis Vlasenko
2006-05-12 15:31 ` Tomasz Malesinski
2006-05-15 11:36 ` Bart Hartgers
2006-05-15 11:46 ` Andi Kleen
2006-05-15 13:36 ` linux-os (Dick Johnson)
2006-05-15 14:19 ` Bart Hartgers
2006-05-12 14:07 ` linux-os (Dick Johnson)
2006-05-12 14:20 ` Denis Vlasenko
2006-05-12 14:42 ` linux-os (Dick Johnson)
2006-05-12 14:53 ` Denis Vlasenko
2006-05-15 20:53 ` Bill Davidsen
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=20060515184401.GA89194@muc.de \
--to=ak@muc.de \
--cc=linux-kernel@vger.kernel.org \
--cc=stsp@aknet.ru \
/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.