From: Paul Mundt <lethal@linux-sh.org>
To: David Howells <dhowells@redhat.com>
Cc: vapier.adi@gmail.com, rgetz@blackfin.uclinux.org,
gerg@uclinux.org, uclinux-dist-devel@blackfin.uclinux.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] FDPIC: Ignore the loader's PT_GNU_STACK when calculating the stack size
Date: Fri, 3 Jul 2009 02:21:08 +0900 [thread overview]
Message-ID: <20090702172108.GA3951@linux-sh.org> (raw)
In-Reply-To: <20090701120814.30741.10146.stgit@warthog.procyon.org.uk>
On Wed, Jul 01, 2009 at 01:08:14PM +0100, David Howells wrote:
> Ignore the loader's PT_GNU_STACK when calculating the stack size, and only
> consider the executable's PT_GNU_STACK, assuming the executable has one.
>
> Currently the behaviour is to take the largest stack size and use that, but
> that means you can't reduce the stack size in the executable. The loader's
> stack size should probably only be used when executing the loader directly.
>
> WARNING: This patch is slightly dangerous - it may render a system inoperable
> if the loader's stack size is larger than that of important executables, and
> the system relies unknowingly on this increasing the size of the stack.
>
> Signed-off-by: David Howells <dhowells@redhat.com>
Works for me too.
Acked-by: Paul Mundt <lethal@linux-sh.org>
next prev parent reply other threads:[~2009-07-02 17:21 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-01 12:08 [PATCH] FDPIC: Ignore the loader's PT_GNU_STACK when calculating the stack size David Howells
2009-07-01 16:02 ` Mike Frysinger
2009-07-01 16:49 ` David Howells
2009-07-01 16:48 ` [PATCH] FDPIC: Ignore the loader's PT_GNU_STACK when calculating the stack size [ver #2] David Howells
2009-07-01 16:49 ` David Howells
2009-07-02 17:21 ` Paul Mundt [this message]
2009-07-04 2:46 ` [PATCH] FDPIC: Ignore the loader's PT_GNU_STACK when calculating the stack size Pavel Machek
2009-07-08 11:01 ` David Howells
2009-07-04 3:34 ` Pavel Machek
2009-07-08 18:48 ` Mike Frysinger
2009-07-09 10:19 ` Pavel Machek
2009-07-09 10:59 ` David Howells
2009-07-11 21:30 ` Pavel Machek
2009-07-14 12:15 ` Mike Frysinger
2009-07-18 10:39 ` Pavel Machek
2009-07-18 19:11 ` Mike Frysinger
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=20090702172108.GA3951@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=dhowells@redhat.com \
--cc=gerg@uclinux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rgetz@blackfin.uclinux.org \
--cc=uclinux-dist-devel@blackfin.uclinux.org \
--cc=vapier.adi@gmail.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.