[PATCH]Add JFFS2 eraseblock header support

Jörn Engel joern at wohnheim.fh-wedel.de
Tue Sep 20 07:36:16 EDT 2005

On Tue, 20 September 2005 14:59:43 +0400, Artem B. Bityutskiy wrote:
> On Tue, 2005-09-20 at 12:24 +0200, Jörn Engel wrote:
> > > 4 old JFFS2 binaries reject mounting new JFFS2 images
> > 
> > Why this?
> Because he changed cleanmarker to the EB header (eraseblock header). Old
> binaries got confused by this since there are working no compatibility
> flags in cleanmarkers. 

WTF?  Old code can simply delete the EB.  You lost all the goodies
from EB, sure, but they are only optimization.  So who cares?

> Moreover, we are going to implement the 1:1 mapping at the same time.
> If old binary mounts new image, it starts writing its cleanmarkers, use
> 1:N mapping etc. A "mixed" image appears. Afterwords, if this mixed
> image is being mounted on new JFFS2 binary, what poor Zhao is supposed
> to do? There will be too much ugliness in the code to handle that.

Please don't mix those two problems.  1:1 mapping has been dealt with.
If you don't like how it has been dealt with, complain in the context
of 1:1 mapping.


When in doubt, use brute force.
-- Ken Thompson

More information about the linux-mtd mailing list