[PATCH] Adding eraseblock header support(revised version)

[Jörn Engel]

On Fri, 23 September 2005 10:45:00 +0800, zhao forrest wrote:
> >
> 1 According to the later disscusion in "1:1 mapping" thread, we should
> reject mounting when detect cross-boundary. In another word, we should
> not reject mounting if we don't detect cross-boundary. Right? This is
> just what my patch implemented :)
> 
> 2 The reason why we introduce JFFS2_NODETYPE_INODE_EBH has nothing to
> do with "when an old JFFS2 image is mounted by new JFFS2 code". It's
> related with "when an new JFFS2 image is mounted by old JFFS2 code".
> Your original design mail for eraseblock header has a clear description
> of it.
> So the problem is still open:
> Whether should we set the compat flag of eraseblock_header to
> RWCOMPAT_DELETE or INCOMPAT???

That's still a problem of the virtual mapping desaster.  I refuse to
discuss it in the context of erase block headers. ;)

Jörn

-- 
ticks = jiffies;
while (ticks == jiffies);
ticks = jiffies;
-- /usr/src/linux/init/main.c