jffs2: Erase pending blocks in GC pass, avoid invalid -EIO return
jffs2_garbage_collect_pass() would previously return -EAGAIN if it couldn't find anything to garbage collect from, and there were blocks on the erase_pending_list. If the blocks were actually in the process of being erased, though, then they wouldn't be on that list. Check for nr_erasing_blocks being non-zero instead. Fix jffs2_reserve_space() to wait for the in-progress erases to complete, when jffs2_garbage_collect_pass() returns -EAGAIN. And fix jffs2_erase_succeeded() to actually wake up the erase_wait wq that jffs2_reserve_space() is now using. Signed-off-by: David Woodhouse <David.Woodhouse@intel.com>
This commit is contained in:
@@ -214,6 +214,19 @@ int jffs2_garbage_collect_pass(struct jffs2_sb_info *c)
|
||||
return ret;
|
||||
}
|
||||
|
||||
/* If there are any blocks which need erasing, erase them now */
|
||||
if (!list_empty(&c->erase_complete_list) ||
|
||||
!list_empty(&c->erase_pending_list)) {
|
||||
spin_unlock(&c->erase_completion_lock);
|
||||
D1(printk(KERN_DEBUG "jffs2_garbage_collect_pass() erasing pending blocks\n"));
|
||||
if (jffs2_erase_pending_blocks(c, 1)) {
|
||||
mutex_unlock(&c->alloc_sem);
|
||||
return 0;
|
||||
}
|
||||
D1(printk(KERN_DEBUG "No progress from erasing blocks; doing GC anyway\n"));
|
||||
spin_lock(&c->erase_completion_lock);
|
||||
}
|
||||
|
||||
/* First, work out which block we're garbage-collecting */
|
||||
jeb = c->gcblock;
|
||||
|
||||
@@ -222,7 +235,7 @@ int jffs2_garbage_collect_pass(struct jffs2_sb_info *c)
|
||||
|
||||
if (!jeb) {
|
||||
/* Couldn't find a free block. But maybe we can just erase one and make 'progress'? */
|
||||
if (!list_empty(&c->erase_pending_list)) {
|
||||
if (c->nr_erasing_blocks) {
|
||||
spin_unlock(&c->erase_completion_lock);
|
||||
mutex_unlock(&c->alloc_sem);
|
||||
return -EAGAIN;
|
||||
|
Reference in New Issue
Block a user