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]

Date:	Wed, 6 Jun 2007 17:59:50 -0500
From:	Matt Mackall <mpm@...enic.com>
To:	Jared Hulbert <jaredeh@...il.com>
Cc:	Christoph Hellwig <hch@...radead.org>, carsteno@...ibm.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 Wed, Jun 06, 2007 at 11:40:58AM -0700, Jared Hulbert wrote:
> > The embedded people already use them
> >on flash which is a little dumb, but now we add even more cludge for
> >a non-block based access.
> 
> Please justify your assertion that using cramfs on flash is dumb.
> What would be not dumb?  In an embedded system with addressable Flash
> the linear addressing cramfs is simple and elegant solution.

Have to agree with Jared here, cramfs is a perfectly sensible thing to
use on many platforms. 

Adding the ability to make particular files XIP on those platforms is
also quite reasonable. 

The alternative would be to add a whole new filesystem to the kernel
(effectively obsoleting cramfs) just to add XIP support or to compile
in a second filesystem (ext2 w/XIP) just for a few files.

Keeping cramfs as a simple example filesystem is really not all that
worthwhile, given it's not much of an example.

-- 
Mathematics is the supreme nostalgia of our time.
-
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/