From: James Bottomley <James.Bottomley@steeleye.com>
To: Joel Soete <jsoe0708@tiscali.be>
Cc: parisc-linux@parisc-linux.org
Subject: RE: [parisc-linux] [PATCH] fix arbitrary limits on stack size
Date: 14 Jul 2003 14:47:14 -0500 [thread overview]
Message-ID: <1058212036.2966.13.camel@mulgrave> (raw)
In-Reply-To: <3F0BEA8300001164@ocpmta1.freegates.net>
On Mon, 2003-07-14 at 05:48, Joel Soete wrote:
> I don' t remember the historical reason of this choice but do you think it
> is possible to back-port it into 2.4 (it will facilitate so much the merge
> with upstream?)
Well, I suppose, theoretically.
However, before we consider backporting, what I really need is for
people to test it. Downward growing mappings may cause application
issues: If you map to an unspecified address, you may be surprised to
discover that you can't expand the mapping upwards. Of course, no
application should ever depend on being able to expand unspecified maps
in either direction, but you never know...
James
next prev parent reply other threads:[~2003-07-14 19:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-12 17:15 [parisc-linux] [PATCH] fix arbitrary limits on stack size James Bottomley
2003-07-14 10:48 ` Joel Soete
2003-07-14 11:58 ` Matthew Wilcox
2003-07-14 19:47 ` James Bottomley [this message]
2003-07-16 17:30 ` Joel Soete
2003-07-16 17:36 ` Matthew Wilcox
2003-07-17 9:52 ` Joel Soete
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=1058212036.2966.13.camel@mulgrave \
--to=james.bottomley@steeleye.com \
--cc=jsoe0708@tiscali.be \
--cc=parisc-linux@parisc-linux.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