linux-kernel - Re: [PATCH 2.6.21] cramfs: add cramfs Linear XIP

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20070608072609.GA13115@infradead.org>
Date:	Fri, 8 Jun 2007 08:26:09 +0100
From:	Christoph Hellwig <hch@...radead.org>
To:	carsteno@...ibm.com
Cc:	Christoph Hellwig <hch@...radead.org>,
	Jared Hulbert <jaredeh@...il.com>,
	Nick Piggin <nickpiggin@...oo.com.au>,
	Andrew Morton <akpm@...ux-foundation.org>,
	richard.griffiths@...driver.com,
	Richard Griffiths <res07ml0@...izon.net>,
	Linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2.6.21] cramfs: add cramfs Linear XIP

On Fri, Jun 08, 2007 at 09:17:18AM +0200, Carsten Otte wrote:
> Christoph Hellwig wrote:
> >On Thu, Jun 07, 2007 at 07:07:54PM +0200, Carsten Otte wrote:
> >>I've had a few beer long discussion with Joern Engel and David 
> >>Woodhouse on this one. To cut a long discussion short: the current XIP 
> >>infrastructure is not sufficient to be used on top of mtd. We'd need 
> >>some extenstions:
> >>- on get_xip_page() we'd need to state if we want the reference 
> >>read-only or read+write
> >>- we need a put_xip_page() to return references
> >>- and finally we need a callback for the referece, so that the mtd 
> >>driver can ask to get its reference back (in order to unmap from 
> >>userland when erasing a block)
> >
> >And we'll need that even when using cramfs.  There's not way we'd
> >merge a hack where the user has to specify a physical address on
> >the mount command line.
> Nay, the proposed solution is read only. From what I understood of the 
> discussion, it does'nt need that. The entire flash memory can be read 
> at the same time. Things start to get interresting when you want to 
> write, then you need to care about erase blocks and such.

We can have a simpler variant as a start if we really want.  But we
need to pass it through the mtd layer.  There is a reason we have this
thing called devices drivers, and we don't want to add knowledge of
ioremap to the filesystems and have users find out physical addresses
of their flash to pass it as mount option.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/