From: Ingo Molnar <mingo@elte.hu>
To: Heiko Carstens <heiko.carstens@de.ibm.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
lethal@linux-sh.org, paulus@samba.org, benh@kernel.crashing.org,
Andrew Morton <akpm@linux-foundation.org>,
Martin Schwidefsky <schwidefsky@de.ibm.com>,
linux-kernel@vger.kernel.org, linux-s390@vger.kernel.org,
Roland McGrath <roland@redhat.com>
Subject: Re: [GIT PULL] s390 updates for 2.6.28-rc1
Date: Fri, 24 Oct 2008 13:37:24 +0200 [thread overview]
Message-ID: <20081024113724.GA21375@elte.hu> (raw)
In-Reply-To: <20081024105049.GC4620@osiris.boeblingen.de.ibm.com>
* Heiko Carstens <heiko.carstens@de.ibm.com> wrote:
> The s390 vdso preparation patch "arch_setup_additional_pages argument"
> touches other architectures (x86, sh and powerpc):
>
> arch_setup_additional_pages currently gets two arguments, the binary
> format descripton and an indication if the process uses an executable
> stack or not. The second argument is not used by anybody, it could be
> removed without replacement.
hm, this is the first time i've seen this change, and it looks a bit
weird:
--- a/arch/x86/include/asm/elf.h
+++ b/arch/x86/include/asm/elf.h
@@ -325,7 +325,7 @@ struct linux_binprm;
#define ARCH_HAS_SETUP_ADDITIONAL_PAGES 1
extern int arch_setup_additional_pages(struct linux_binprm *bprm,
- int executable_stack);
+ int uses_interp);
why didnt you just add a new uses_interp argument?
executable_stack is passed in to potentially enable architectures to be
aware of how conservative/legacy the address-space of the binary is -
whether to randomize the vdso, etc. exec-shield used to take advantage
of that.
But there seems to be no in-tree use of that (and if one arises it can
just add back that parameter), and i dont want to stand in the way of
your pull request either, so for the x86 bits:
Acked-by: Ingo Molnar <mingo@elte.hu>
Ingo
next prev parent reply other threads:[~2008-10-24 11:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-24 10:50 [GIT PULL] s390 updates for 2.6.28-rc1 Heiko Carstens
2008-10-24 11:37 ` Ingo Molnar [this message]
2008-10-26 18:26 ` Martin Schwidefsky
2008-10-27 11:51 ` Ingo Molnar
2008-10-27 12:32 ` Martin Schwidefsky
2008-10-27 18:11 ` Ingo Molnar
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=20081024113724.GA21375@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=benh@kernel.crashing.org \
--cc=heiko.carstens@de.ibm.com \
--cc=lethal@linux-sh.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=paulus@samba.org \
--cc=roland@redhat.com \
--cc=schwidefsky@de.ibm.com \
--cc=torvalds@linux-foundation.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