From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Arjan van de Ven <arjan@linux.intel.com>
Cc: akpm@osdl.org, linux-arch@vger.kernel.org, jbaron@redhat.com,
ak@muc.de, benh@kernel.crashing.org, geert@linux-m68k.org,
hugh@veritas.com, kkojima@rr.iij4u.or.jp, lethal@linux-sh.org,
paulus@samba.org, rmk@arm.linux.org.uk, spyro@f2s.com,
tony.luck@intel.com, zippel@linux-m68k.org
Subject: Re: [patch 1/1] make PROT_WRITE imply PROT_READ
Date: Fri, 15 Sep 2006 12:10:08 +0100 [thread overview]
Message-ID: <1158318608.29932.9.camel@localhost.localdomain> (raw)
In-Reply-To: <450A31D4.1020108@linux.intel.com>
Ar Gwe, 2006-09-15 am 06:53 +0200, ysgrifennodd Arjan van de Ven:
> This patch will create a userspace ABI precedent that will hurt us if we ever
> decide to implement this, or if Intel or AMD add support for this to the cpu...
You mean like noexec didn't. It's just a question of binary type if such
a mapping type comes into existance. At the moment the behaviour is
essentially random.
Alan
next prev parent reply other threads:[~2006-09-15 10:47 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-15 1:39 [patch 1/1] make PROT_WRITE imply PROT_READ akpm
2006-09-15 4:53 ` Arjan van de Ven
2006-09-15 11:10 ` Alan Cox [this message]
2006-09-15 8:06 ` Geert Uytterhoeven
2006-09-15 10:58 ` Alan Cox
2006-09-15 8:47 ` Andi Kleen
2006-09-15 11:12 ` Alan Cox
2006-09-16 0:40 ` Ralf Baechle
2006-09-17 11:59 ` Paul Mundt
2006-09-17 20:24 ` Chris Wedgwood
2006-09-17 20:48 ` Arjan van de Ven
2006-09-17 21:14 ` Alan Cox
2006-09-17 21:05 ` Arjan van de Ven
2006-09-18 0:57 ` Chris Wedgwood
2006-09-18 2:03 ` Paul Mackerras
2006-09-18 4:31 ` Chris Wedgwood
2006-09-18 8:15 ` Geert Uytterhoeven
2006-09-18 9:26 ` Alan Cox
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=1158318608.29932.9.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=ak@muc.de \
--cc=akpm@osdl.org \
--cc=arjan@linux.intel.com \
--cc=benh@kernel.crashing.org \
--cc=geert@linux-m68k.org \
--cc=hugh@veritas.com \
--cc=jbaron@redhat.com \
--cc=kkojima@rr.iij4u.or.jp \
--cc=lethal@linux-sh.org \
--cc=linux-arch@vger.kernel.org \
--cc=paulus@samba.org \
--cc=rmk@arm.linux.org.uk \
--cc=spyro@f2s.com \
--cc=tony.luck@intel.com \
--cc=zippel@linux-m68k.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