From: ebiederm@xmission.com (Eric W. Biederman)
To: Kees Cook <keescook@chromium.org>
Cc: Dave Hansen <dave@sr71.net>,
Andrew Morton <akpm@linux-foundation.org>,
"Theodore Ts'o" <tytso@mit.edu>, Oleg Nesterov <oleg@redhat.com>,
LKML <linux-kernel@vger.kernel.org>,
Dave Hansen <dave.hansen@linux.intel.com>
Subject: Re: [RFC][PATCH 1/2] fs proc: make pagemap a privileged interface
Date: Mon, 09 Mar 2015 18:43:00 -0500 [thread overview]
Message-ID: <878uf5rb3v.fsf@x220.int.ebiederm.org> (raw)
In-Reply-To: <87h9ttrcpr.fsf@x220.int.ebiederm.org> (Eric W. Biederman's message of "Mon, 09 Mar 2015 18:08:16 -0500")
A 1 to 1 blinding function like integer multiplication mudulo 2^32 by an
appropriate random number ought to keep from revealing page numbers or
page ajacencies while not requiring any changes in userspace.
That way the revealed pfn and the physcial pfn would be different but
you could still use pagemap for it's intended purpose.
Eric
next prev parent reply other threads:[~2015-03-09 23:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20150309204321.AAF412E0@viggo.jf.intel.com>
2015-03-09 21:31 ` Kees Cook
[not found] ` <20150309204322.50DA6B5D@viggo.jf.intel.com>
2015-03-09 21:32 ` [RFC][PATCH 2/2] proc: config options for making privileged /proc the default Kees Cook
2015-03-09 22:13 ` [RFC][PATCH 1/2] fs proc: make pagemap a privileged interface Eric W. Biederman
2015-03-09 22:22 ` Kees Cook
2015-03-09 23:08 ` Eric W. Biederman
2015-03-09 23:40 ` Kees Cook
2015-03-09 23:43 ` Eric W. Biederman [this message]
2015-03-10 0:03 ` Kees Cook
2015-03-10 2:51 ` Dave Hansen
2015-03-10 4:49 ` Eric W. Biederman
2015-03-10 2:28 ` Dave Hansen
2015-03-12 22:35 ` Andrew Morton
2015-03-13 15:56 ` Dave Hansen
2015-03-13 17:16 ` Eric W. Biederman
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=878uf5rb3v.fsf@x220.int.ebiederm.org \
--to=ebiederm@xmission.com \
--cc=akpm@linux-foundation.org \
--cc=dave.hansen@linux.intel.com \
--cc=dave@sr71.net \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg@redhat.com \
--cc=tytso@mit.edu \
/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
Powered by JetHome