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:	Thu, 7 Jun 2007 14:11:44 -0700
From:	"Jared Hulbert" <jaredeh@...il.com>
To:	"Christoph Hellwig" <hch@...radead.org>,
	"Jared Hulbert" <jaredeh@...il.com>, 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

> that even more important doesn't require pulling in
> the whole block layer which is especially important for embedded
> devices at the lower end of the scala.

Good point.  That is a big oversight.  Though I would prefer to handle
that in the same fs rather than fork.

> I still think it'd be even better to just
> hook xip support into jffs or logfs because they give you a full
> featured flash filesystem for all needs without the complexity
> of strictly partitioning between xip-capable and write parts
> of your storage.

This is nirvana.   But it is not the goal of the patches in question.
In fact there are several use cases that don't need and don't value
the writeability and don't need therefore the overhead.  It is a long
term goal never the less.
-
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/