linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: Scott Wood <scottwood@freescale.com>,
	Linuxppc-dev Development <linuxppc-dev@ozlabs.org>
Subject: Re: issues w/init
Date: Fri, 17 Apr 2009 09:38:27 +0200	[thread overview]
Message-ID: <1239953907.7443.45.camel@pasglop> (raw)
In-Reply-To: <C17084D8-19F7-48D2-8E7E-2DE561108A90@kernel.crashing.org>

On Thu, 2009-04-16 at 14:27 -0500, Kumar Gala wrote:
> On Apr 16, 2009, at 2:25 PM, Scott Wood wrote:
> 
> > Kumar Gala wrote:
> >> [root:~] cat /proc/1/maps
> >> 00100000-00103000 r-xp 00100000 00:00 0          [vdso]
> >> 0feab000-0ffbe000 r-xp 00000000 00:0d 7127086    /lib/libc-2.2.5.so
> >> 0ffbe000-0ffcb000 ---p 00113000 00:0d 7127086    /lib/libc-2.2.5.so
> >> 0ffcb000-0ffeb000 rw-p 00110000 00:0d 7127086    /lib/libc-2.2.5.so
> >
> > IIRC, this libc is old enough to execute out of non-exec memory in  
> > some cases.
> 
> Yeah, I'm going to that realization.  The question is are we ok with  
> breaking older versions of libc like this.

I'm pretty sure they are broken already when running off a 64-bit
kernel, but yeah, as I said, we may want a .config option to enable
support for that old junk which also disables support from per-page
execute permission.

Ben.

  reply	other threads:[~2009-04-17  7:40 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 [this message]
2009-04-17 10:05         ` Paul Mackerras
2009-04-17 10:33           ` Benjamin Herrenschmidt
2009-04-17 10:41           ` Benjamin Herrenschmidt
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=1239953907.7443.45.camel@pasglop \
    --to=benh@kernel.crashing.org \
    --cc=galak@kernel.crashing.org \
    --cc=linuxppc-dev@ozlabs.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).