From: Marco <marco.stornelli@gmail.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: "David Woodhouse" <dwmw2@infradead.org>,
"Jörn Engel" <joern@lazybastard.org>,
"Sam Ravnborg" <sam@ravnborg.org>,
"Tim Bird" <tim.bird@am.sony.com>,
"Chris Simmonds" <chris@2net.co.uk>,
"Linux FS Devel" <linux-fsdevel@vger.kernel.org>,
"Linux Embedded" <linux-embedded@vger.kernel.org>,
"Linux Kernel" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 06/14] Pramfs: Include files
Date: Wed, 24 Jun 2009 18:49:41 +0200 [thread overview]
Message-ID: <4A425925.7000601@gmail.com> (raw)
In-Reply-To: <200906241730.37151.arnd@arndb.de>
Arnd Bergmann wrote:
> On Wednesday 24 June 2009, Marco Stornelli wrote:
>>> Actually, reading from /dev/mem is only valid on real RAM. If the nvram
>>> is part of an IO memory mapping, you have to do mmap()+memcpy() rather
>>> than read(). So dd won't do it, but it's still easy to read from user
>>> space.
>> For "security" reasons pram reserve the region of memory with
>> reserve_mem_region_exclusive().....
>
> That will only prevent other device drivers from stepping on it,
> /dev/mem does not care about mem_region reservations.
>
> Arnd <><
>
Userland may not map this resource, so /dev/mem and the sysfs MMIO
access will not be allowed. This restriction depends on STRICT_DEVMEM
option. It's true that currently is only implemented in the x86 world.
Marco
next prev parent reply other threads:[~2009-06-24 16:49 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-13 13:21 [PATCH 06/14] Pramfs: Include files Marco
2009-06-13 14:04 ` Sam Ravnborg
2009-06-13 22:59 ` Arnd Bergmann
2009-06-14 7:15 ` Marco
2009-06-21 17:07 ` Marco
2009-06-21 20:22 ` Arnd Bergmann
2009-06-22 6:23 ` Marco Stornelli
2009-06-22 11:17 ` Arnd Bergmann
2009-06-22 18:05 ` Marco
2009-06-22 18:33 ` Arnd Bergmann
2009-06-22 19:31 ` Chris Simmonds
2009-06-22 20:30 ` Sam Ravnborg
2009-06-22 22:00 ` Tim Bird
2009-06-23 4:21 ` Sam Ravnborg
2009-06-23 17:38 ` Marco
2009-06-23 19:26 ` Jörn Engel
2009-06-23 21:15 ` David Woodhouse
2009-06-23 21:55 ` Arnd Bergmann
2009-06-24 6:32 ` Marco Stornelli
2009-06-24 15:30 ` Arnd Bergmann
2009-06-24 16:49 ` Marco [this message]
2009-06-22 21:41 ` Jörn Engel
2009-06-22 22:20 ` David Woodhouse
2009-06-23 5:57 ` Jörn Engel
2009-06-23 8:31 ` David Woodhouse
2009-06-22 23:07 ` Arnd Bergmann
2009-06-23 6:40 ` Marco Stornelli
2009-06-14 7:15 ` Marco
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=4A425925.7000601@gmail.com \
--to=marco.stornelli@gmail.com \
--cc=arnd@arndb.de \
--cc=chris@2net.co.uk \
--cc=dwmw2@infradead.org \
--cc=joern@lazybastard.org \
--cc=linux-embedded@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.org \
--cc=tim.bird@am.sony.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;
as well as URLs for NNTP newsgroup(s).