linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Scott Wood <scottwood@freescale.com>
Cc: linuxppc-dev@ozlabs.org, paulus@samba.org
Subject: Re: Executing from readablee, no-exec pages
Date: Sat, 07 Jul 2007 12:33:32 +1000	[thread overview]
Message-ID: <1183775612.3388.193.camel@localhost.localdomain> (raw)
In-Reply-To: <20070706164942.GA10806@ld0162-tx32.am.freescale.net>


> Well, it means that leaving VM_READ out of the check (except where the
> hardware PTE has an exec bit) isn't really buying us anything
> security-wise (especially since the primary reason for no-exec protection
> is to avoid code injections via stack overflow, and those pages will
> usually already be present), so it doesn't hurt much to let things keep
> working.
> 
> At the least, I'd like it to keep working for a few more kernel releases
> (with a warning printed when a VM_EXEC-only test would have failed), so
> people have time to upgrade glibc.

I agree. Care to send a patch ? :-0

Ben.

  reply	other threads:[~2007-07-07  2:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-05 21:55 Executing from readablee, no-exec pages Scott Wood
2007-07-05 22:38 ` Rodrigo Rubira Branco
2007-07-06 11:18 ` Johannes Berg
2007-07-06 13:36   ` Segher Boessenkool
2007-07-06 13:43     ` Johannes Berg
2007-07-06 13:24 ` Segher Boessenkool
2007-07-06 16:49   ` Scott Wood
2007-07-07  2:33     ` Benjamin Herrenschmidt [this message]
2007-07-06 14:42 ` David Woodhouse
2007-07-07  2: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=1183775612.3388.193.camel@localhost.localdomain \
    --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).