From: Mike Frysinger <vapier.adi@gmail.com>
To: David Howells <dhowells@redhat.com>
Cc: rgetz@blackfin.uclinux.org, lethal@linux-sh.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: Wed, 1 Jul 2009 12:02:28 -0400 [thread overview]
Message-ID: <8bd0f97a0907010902y4c6b4d86m36a1116d5af67f0@mail.gmail.com> (raw)
In-Reply-To: <20090701120814.30741.10146.stgit@warthog.procyon.org.uk>
On Wed, Jul 1, 2009 at 08:08, David Howells wrote:
> 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.
every toolchain ive seen sets the stack size in the linker to the
default value, and the only way to change that is to manually set the
size yourself with the relevant command line option. so it's only
going to break people who have been doing it wrong themselves --
setting the stack size to a smaller option than is acceptable.
> - else
> + else
this change just adds trailing whitespace ...
otherwise, just tested it and it works for me, thanks
Signed-off-by: Mike Frysinger <vapier@gentoo.org>
-mike
next prev parent reply other threads:[~2009-07-01 16:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-01 12:08 David Howells
2009-07-01 16:02 ` Mike Frysinger [this message]
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 ` [PATCH] FDPIC: Ignore the loader's PT_GNU_STACK when calculating the stack size David Howells
2009-07-01 16:49 ` [PATCH] FDPIC: Ignore the loader's PT_GNU_STACK when calculating the stack size [ver #2] David Howells
2009-07-02 17:21 ` [PATCH] FDPIC: Ignore the loader's PT_GNU_STACK when calculating the stack size Paul Mundt
2009-07-04 2:46 ` 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=8bd0f97a0907010902y4c6b4d86m36a1116d5af67f0@mail.gmail.com \
--to=vapier.adi@gmail.com \
--cc=dhowells@redhat.com \
--cc=gerg@uclinux.org \
--cc=lethal@linux-sh.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rgetz@blackfin.uclinux.org \
--cc=uclinux-dist-devel@blackfin.uclinux.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
all inboxes | Powered by JetHome®