mkfs.jffs2.c rework

David Woodhouse dwmw2 at
Mon Nov 25 07:12:33 EST 2002

andersen at said:
>  Hmm.  Ok, your're the boss.  I guess we can pretend it's always 4096
> as long as the kernel code is doing the right thing.  It looked like
> the kernel code was assuming the block size matched the page cache
> size.  No big deal. 

We assume that no node crosses a page boundary. It's fine for there to be 
nodes which are _smaller_ than a page, just not larger. 

>  I suppose so, the code is pretty clean now I think.   Whats a
> cleanmarker?  :)

Small node written to the beginning of each erased block to mark it as 
being properly erased. Otherwise the JFFS2 code will erase it again just to 
make sure. Currently we do this for the free space in a partition after 
it's first mounted -- if our jffs2 image is padded to the right length and 
has cleanmarkers in, we wouldn't need to.

I don't think we want it to be the default though -- we'd have to ensure 
the erase size was correct if we did that. 


More information about the linux-mtd mailing list