From: "Mike Frysinger" <vapier.adi@gmail.com>
To: "Pekka J Enberg" <penberg@cs.helsinki.fi>
Cc: "Wu, Bryan" <bryan.wu@analog.com>,
"David Howells" <dhowells@redhat.com>,
"Andrew Morton" <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, "Hugh Dickins" <hugh@veritas.com>,
"Alan Cox" <alan@lxorguk.ukuu.org.uk>
Subject: Re: [PATCH -mm] Revoke core code: fix nommu arch compiling error bug
Date: Tue, 27 Mar 2007 03:20:33 -0400 [thread overview]
Message-ID: <8bd0f97a0703270020m67821b90gb9d1cdfd6262887b@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0703270955490.32526@sbz-30.cs.Helsinki.FI>
On 3/27/07, Pekka J Enberg <penberg@cs.helsinki.fi> wrote:
> On Tue, 27 Mar 2007, Wu, Bryan wrote:
> > Agree. MPU of Blackfin can provide some processes protection. But maybe
> > at this moment just disable revoke for NOMMU is easier for further
> > development. When we provide the MPU stuff, maybe we can enable the
> > revoke for NOMMU but MPU arch.
>
> Yeah, MPU should be sufficient for revoke(). Note that mmap() and mummap()
> suffers from the same problem on NOMMU so perhaps we really should do
> CONFIG_MPU.
we would need both ... MPU gives us the ability to restrict access,
but we'd still be unable to do fun things like COW
-mike
next prev parent reply other threads:[~2007-03-27 7:20 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-26 10:23 Wu, Bryan
2007-03-26 10:37 ` Pekka J Enberg
2007-03-26 10:41 ` Andrew Morton
2007-03-26 11:25 ` David Howells
2007-03-26 11:30 ` Pekka J Enberg
2007-03-26 11:44 ` David Howells
2007-03-26 11:55 ` Pekka J Enberg
2007-03-26 12:22 ` David Howells
2007-03-26 12:37 ` Pekka J Enberg
2007-03-26 13:24 ` David Howells
2007-03-26 20:21 ` Mike Frysinger
2007-03-27 3:29 ` Wu, Bryan
2007-03-27 6:57 ` Pekka J Enberg
2007-03-27 7:20 ` Mike Frysinger [this message]
2007-03-27 10:05 ` David Howells
2007-03-27 17:00 ` Mike Frysinger
2007-03-27 19:06 ` David Howells
2007-03-26 13:03 ` Alan Cox
2007-03-26 11:50 ` Andrew Morton
2007-03-26 11:58 ` David Howells
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=8bd0f97a0703270020m67821b90gb9d1cdfd6262887b@mail.gmail.com \
--to=vapier.adi@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bryan.wu@analog.com \
--cc=dhowells@redhat.com \
--cc=hugh@veritas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=penberg@cs.helsinki.fi \
/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
all inboxes | Powered by JetHome®