From: David Howells <dhowells@redhat.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: dhowells@redhat.com, vapier.adi@gmail.com,
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, 08 Jul 2009 12:01:40 +0100 [thread overview]
Message-ID: <24530.1247050900@redhat.com> (raw)
In-Reply-To: <20090704024606.GE1345@ucw.cz>
Pavel Machek <pavel@ucw.cz> wrote:
> The patch seems wrong to me; loader needs the stack, too, right?
>
> What about making sure that the loader specifies reasonable stack
> size, instead?
The loader doesn't need its own stack, unless it _is_ the executable. It uses
the executable's stack. The problem is that the executable and the loader can
both specify the stack size for NOMMU, but which one do we pick, or do we
consider both.
David
next prev parent reply other threads:[~2009-07-08 11:03 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 ` [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 [this message]
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=24530.1247050900@redhat.com \
--to=dhowells@redhat.com \
--cc=gerg@uclinux.org \
--cc=lethal@linux-sh.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--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.