failed write verify causes segmentation fault
sergei.sharonov at halliburton.com
Thu Mar 17 13:20:57 EST 2005
> > This is only one possible reason. The other possible reason which I
> > think is more likely has happened in your case is that JFFS2 tried to
> > write to a non-empty NAND page, e.g., the page didn't contain all 0xFF.
> > In this case write_verify() might fail as well. I don't know why JFFS2
> > might do that, possibly there is some bug.
> The question is not why the write verify fails. In his test environment
> a page failure is expected to happen at some point. The question is why
> JFFS2 did not cope with the problem as it is supposed to be.
Exactly. Could not have said better myself. How should jffs2 handle failed
writes? Replace bad page transparently on the fly, return number of bytes
written < number of bytes requested, segfault ;-) ?
P.S. For you, poor souls stuck behind corporate firewalls with Outlook/Exchange,
it looks like gmane.org is a good alternative. It does threading, posts plain
text and checks for >80 chars/lines.
More information about the linux-mtd