From: "Serge E. Hallyn" <serue@us.ibm.com>
To: Pekka J Enberg <penberg@cs.helsinki.fi>
Cc: "Serge E. Hallyn" <serue@us.ibm.com>,
Christoph Hellwig <hch@infradead.org>,
Arjan van de Ven <arjan@infradead.org>,
Mimi Zohar <zohar@us.ibm.com>,
akpm@osdl.org, kjhall@linux.vnet.ibm.com,
linux-kernel@vger.kernel.org, safford@saff.watson.ibm.com
Subject: Re: mprotect abuse in slim
Date: Wed, 10 Jan 2007 09:58:45 -0600 [thread overview]
Message-ID: <20070110155845.GA373@sergelap.austin.ibm.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0701100914550.22496@sbz-30.cs.Helsinki.FI>
Quoting Pekka J Enberg (penberg@cs.helsinki.fi):
> On Tue, 9 Jan 2007, Serge E. Hallyn wrote:
> > Whatever happened with Pekka's revoke submissions? Did you lose
> > interest after
> > http://www.kernel.org/pub/linux/kernel/people/penberg/patches/revoke/2.6.19-rc1/revoke-2.6.19-rc1,
> > or was it decided that the approach was unworkable?
>
> Lack of time.
Ok great - then it's not dead :)
> Also, I would love to hear comments on the way I am doing
> revoke on shared mappings. There are few open issues remaining, mainly,
> supporting munmap(2) for revoked mappings.
Hmm, I wanted to test your revoke-munmap.c to see what you get right now
with munmap, but a quick port of your patch to yesterdays -git on s390
gives me an oops on do_revoke. I'll have to straighten that out when I
get a chance.
But since it looks like you just munmap the region now, shouldn't a
subsequent munmap by the app just return -EINVAL? that seems appropriate
to me.
thanks,
-serge
next prev parent reply other threads:[~2007-01-10 15:58 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-08 13:41 mprotect abuse in slim Christoph Hellwig
2007-01-08 22:38 ` Mimi Zohar
2007-01-09 3:07 ` Arjan van de Ven
2007-01-09 9:46 ` Christoph Hellwig
2007-01-09 20:54 ` Chris Wright
2007-01-09 23:14 ` Serge E. Hallyn
2007-01-10 7:21 ` Pekka J Enberg
2007-01-10 15:58 ` Serge E. Hallyn [this message]
2007-01-11 7:39 ` Pekka Enberg
2007-01-11 15:49 ` Serge E. Hallyn
2007-01-12 7:43 ` Pekka Enberg
2007-01-12 15:17 ` Serge E. Hallyn
2007-01-12 9:45 ` Pekka Enberg
2007-01-12 19:28 ` Serge E. Hallyn
2007-01-12 19:53 ` Pekka J Enberg
2007-01-09 21:30 ` Mimi Zohar
2007-01-09 19:27 ` Valdis.Kletnieks
2007-01-09 21:45 ` Mimi Zohar
2007-01-11 14:35 ` Pavel Machek
2007-01-12 20:08 ` Mimi Zohar
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=20070110155845.GA373@sergelap.austin.ibm.com \
--to=serue@us.ibm.com \
--cc=akpm@osdl.org \
--cc=arjan@infradead.org \
--cc=hch@infradead.org \
--cc=kjhall@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=penberg@cs.helsinki.fi \
--cc=safford@saff.watson.ibm.com \
--cc=zohar@us.ibm.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