Why the nand chip driver "should never return -EBADMSG if it failed to read all the request data"

[Artem Bityutskiy]

On Sun, 2012-04-15 at 21:49 +0800, Mark wrote:
> And, after I patched the nand driver, in most of the situations the
> UBIFS can be successfully recovered, but I still get this error:
> 
> ...
> UBI error: ubi_io_read: error -77 while reading 126976 bytes from PEB
> 2:4096, read 126976 bytes
> UBIFS error (pid 481): insert_node: duplicate sqnum in replay
> mount: mounting ubi13_0 on /usr/local/hmt/appdata failed: Invalid argument
> ...
> 
> Does this mean this should never happen to UBIFS? Then what could be the 
> reason?
> Thank you very much, and my test environment:

I see ubi_dbg_dump_stack() call in ubi_io_read() when it returns an
error. If you have debugging enabled - you should have the dump in your
kernel buffer.

Yeah, we should turn it into 'dump_stack()' to always have the dump. I'd
gratefully accept a patch.

-- 
Best Regards,
Artem Bityutskiy
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part
URL: <http://lists.infradead.org/pipermail/linux-mtd/attachments/20120422/0d6de760/attachment.sig>