[PATCH]Add JFFS2 eraseblock header support

[Ferenc Havasi]

Dear All,

I just would like to write my opinion about these topics.

I don't think that we should keep absolut monkey-safe compatibility. To
deal still with 1:N images makes the things unnecessary complicated
IMHO. The big warning (what Joern wrote to the list) should be enough
for every serious user. Or there is one more thing what we can do: if we
detect a cross-erase block node we reject mounting/set read-only flag.
Is there anything other (than cross erase block nodes) can be problem
with 1:N => 1:1?

I agree with Joern that erase block header now only a performance
improvement, so it should not be INCOMPAT. I think it would not even
solve the 1:N => 1:1 problem well. It only force the user than if he
uses new utils (mkfs.jffs2, ..) than use new JFFS2, tool; and if he used
a newer JFFS2 code, do not use an older one again. Nothing more. (Did I
misunderstand something?) I don't think that it is a real problem. But
if we afraid of it, I think we should introduce a distict new node type,
and not new types for inodes and dirents.

Bye,
Ferenc

P.S.: Zhao: If your patch reach the final state we will extend the
summary code to handle your node type correctly, too.