mtd-utils: ubiformat: writing images on flash with badblocks.

[Artem Bityutskiy]

On Mon, 2011-09-12 at 08:41 +0200, Ricard Wanderlof wrote:
> > On Sun, 11 Sep 2011, Artem Bityutskiy wrote:
> > 
> > This issue was reported and analyzed by
> > Anton Olofsson <anol.martinsson at gmail.com>:
> > 
> > when ubiformat encounters a write error while flashing the UBI image (which may
> > come from a file of from stdout), it correctly marks the faulty eraseblock as
> > bad and skips it. However, it also incorrectly drops the data buffer which was
> > supposed to be written, and reads next block of data.
> 
> I'm just curious, how come this has gone unnoticed for so long? One would 
> think that someone would have tried to flash an image to a chip with bad 
> blocks a long time ago?

No, bad blocks are handled fine. This is about the situation when an
eraseblock is good, then we write to it, and we get an error, then we
torture it, and the test fails, and we (ubiformat) mark it as bad. This
is very rare situation indeed.

-- 
Best Regards,
Artem Bityutskiy