From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Paul Mackerras <paulus@samba.org>
Cc: Scott Wood <scottwood@freescale.com>,
Linuxppc-dev Development <linuxppc-dev@ozlabs.org>
Subject: Re: issues w/init
Date: Fri, 17 Apr 2009 12:41:00 +0200 [thread overview]
Message-ID: <1239964860.7443.65.camel@pasglop> (raw)
In-Reply-To: <18920.21593.737132.732053@cargo.ozlabs.ibm.com>
On Fri, 2009-04-17 at 20:05 +1000, Paul Mackerras wrote:
> Benjamin Herrenschmidt writes:
>
> > I'm pretty sure they are broken already when running off a 64-bit
> > kernel,
>
> Maybe not... for 64-bit kernels we have our definition of
> elf_read_implies_exec in arch/powerpc/include/asm/elf.h, which IIRC
> sets the read-implies-exec personality thing on old 32-bit binaries.
Ok, so looking at that more closely, if that had worked, we would
have had PROT_EXEC, and thus VM_EXEC added to the vma by mmap... which
apparently didn't occur.
I think what may be happening is that the binary he's running has the
PT_GNU_STACK but his libc doesn't ... the kernel will set the
personality flag based on the binary you are trying to run, not any
library it uses...
Kumar, can you try to instrument that a bit and tell us ? What the
personality flag gets set to and whether mmap sets PROT_EXEC ?
Cheers,
Ben.
next prev parent reply other threads:[~2009-04-17 10:44 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-16 18:21 issues w/init Kumar Gala
2009-04-16 18:53 ` Kumar Gala
2009-04-16 19:25 ` Scott Wood
2009-04-16 19:27 ` Kumar Gala
2009-04-17 7:38 ` Benjamin Herrenschmidt
2009-04-17 10:05 ` Paul Mackerras
2009-04-17 10:33 ` Benjamin Herrenschmidt
2009-04-17 10:41 ` Benjamin Herrenschmidt [this message]
2009-04-17 13:23 ` Kumar Gala
2009-04-17 17:03 ` Benjamin Herrenschmidt
2009-04-17 17:40 ` Kumar Gala
2009-04-17 17:51 ` Benjamin Herrenschmidt
2009-04-17 13:59 ` Kumar Gala
2009-04-17 17:04 ` Benjamin Herrenschmidt
2009-04-17 7:37 ` Benjamin Herrenschmidt
2009-04-17 7:33 ` Benjamin Herrenschmidt
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=1239964860.7443.65.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.org \
--cc=scottwood@freescale.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).