From: Hugh Dickins <hugh@veritas.com>
To: Bjorn Helgaas <bjorn.helgaas@hp.com>
Cc: linux-kernel@vger.kernel.org, Andrew Morton <akpm@osdl.org>,
Tony Luck <tony.luck@intel.com>,
linux-ia64@vger.kernel.org
Subject: Re: [PATCH] /dev/mem validate mmap requests
Date: Tue, 06 Dec 2005 18:39:56 +0000 [thread overview]
Message-ID: <Pine.LNX.4.61.0512061832090.26899@goblin.wat.veritas.com> (raw)
In-Reply-To: <200512051700.20269.bjorn.helgaas@hp.com>
On Mon, 5 Dec 2005, Bjorn Helgaas wrote:
> Add a hook so architectures can validate /dev/mem mmap requests.
Not a comment on your patch at all, just an FYI in case you've missed
it, and in case it makes any difference to your ia64 needs.
A side-effect of 2.6.15-rc's PageReserved changes is that a user with
access to /dev/mem can now mmap any page of it, and see what's there
rather than zeroes, whether or not it has been marked PageReserved.
Hugh
next prev parent reply other threads:[~2005-12-06 18:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-06 0:00 [PATCH] /dev/mem validate mmap requests Bjorn Helgaas
2005-12-06 18:39 ` Hugh Dickins [this message]
2005-12-06 20:49 ` Bjorn Helgaas
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=Pine.LNX.4.61.0512061832090.26899@goblin.wat.veritas.com \
--to=hugh@veritas.com \
--cc=akpm@osdl.org \
--cc=bjorn.helgaas@hp.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tony.luck@intel.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