From: Andrea Arcangeli <andrea@suse.de>
To: Jeff Dike <jdike@karaya.com>
Cc: Linus Torvalds <torvalds@transmeta.com>, linux-kernel@vger.kernel.org
Subject: Re: expand_stack fix [was Re: 2.4.9aa3]
Date: Sun, 9 Sep 2001 05:50:38 +0200 [thread overview]
Message-ID: <20010909055038.M11329@athlon.random> (raw)
In-Reply-To: <20010908180416.Z11329@athlon.random> <200109090423.XAA03403@ccure.karaya.com>
In-Reply-To: <200109090423.XAA03403@ccure.karaya.com>; from jdike@karaya.com on Sat, Sep 08, 2001 at 11:23:38PM -0500
On Sat, Sep 08, 2001 at 11:23:38PM -0500, Jeff Dike wrote:
> andrea@suse.de said:
> > My fix for the race doesn't drop the usability of GROWSDOWN that could
> > otherwise break userspace programs. I guess at least uml uses
> > growsdown vma file backed. Jeff?
>
> No. In neither the host kernel or UML is there a vma that's file backed and
> growsdown.
>
> UML process stacks are marked growsdown in UML and are file backed on the host,
> but that's not the same thing.
ok, so I guess you're doing the growsdown by hand in the uml sigsegv
handler.
So it's probably fine to allow GROWSDOWN only on anon vmas per Linus's
suggestion. I can attempt to change the race fix that way.
However about last Linus's suggestion it's not obvious to me that
dropping GROWSDOWN/UP completly and forcing a fixed virtual size of the
stack [modulo rlimit of course] is a good idea, because:
1) on 32bit platforms having big vma for the stack means reducing the
space for the dynamic mappings
2) I love not to have a virtual stack limit for software making use of
aggressive recursion.
The gap logic is very simple too.
Andrea
next prev parent reply other threads:[~2001-09-09 3:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-19 6:07 2.4.9aa3 Andrea Arcangeli
2001-09-03 15:24 ` expand_stack fix [was Re: 2.4.9aa3] Andrea Arcangeli
2001-09-07 18:47 ` Linus Torvalds
2001-09-08 16:04 ` Andrea Arcangeli
2001-09-08 16:28 ` Linus Torvalds
2001-09-09 4:23 ` Jeff Dike
2001-09-09 3:50 ` Andrea Arcangeli [this message]
2001-09-09 5:42 ` Jeff Dike
2001-09-11 11:24 ` Andrea Arcangeli
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=20010909055038.M11329@athlon.random \
--to=andrea@suse.de \
--cc=jdike@karaya.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 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.