[MTD] mtdoops: Fix a bug where block may not be erased
This makes the driver erase a block when it doesn't find any existing saved log messages which is safer than assuming the flash was already erased. Signed-off-by: Richard Purdie <rpurdie@rpsys.net> Signed-off-by: David Woodhouse <David.Woodhouse@intel.com>
This commit is contained in:
parent
f0482ee366
commit
43b5693d40
1 changed files with 1 additions and 3 deletions
|
@ -258,9 +258,7 @@ static void find_next_position(struct mtdoops_context *cxt)
|
||||||
if (maxcount == 0xffffffff) {
|
if (maxcount == 0xffffffff) {
|
||||||
cxt->nextpage = 0;
|
cxt->nextpage = 0;
|
||||||
cxt->nextcount = 1;
|
cxt->nextcount = 1;
|
||||||
cxt->ready = 1;
|
schedule_work(&cxt->work_erase);
|
||||||
printk(KERN_DEBUG "mtdoops: Ready %d, %d (first init)\n",
|
|
||||||
cxt->nextpage, cxt->nextcount);
|
|
||||||
return;
|
return;
|
||||||
}
|
}
|
||||||
|
|
||||||
|
|
Loading…
Reference in a new issue