[JFFS2] Prevent list corruption when handling write errors
Linux-MTD Mailing List
linux-mtd at lists.infradead.org
Wed Apr 18 04:59:05 EDT 2007
Gitweb: http://git.infradead.org/?p=mtd-2.6.git;a=commit;h=99c2594f0e13de1ca84f97efc3f9e7bc49f91e11
Commit: 99c2594f0e13de1ca84f97efc3f9e7bc49f91e11
Parent: a5ac8aeb29000fcab8d91848273a6616fcd039ee
Author: Adrian Hunter <ext-adrian.hunter at nokia.com>
AuthorDate: Thu Mar 29 11:00:47 2007 +0300
Committer: David Woodhouse <dwmw2 at infradead.org>
CommitDate: Tue Apr 17 13:56:23 2007 -0400
[JFFS2] Prevent list corruption when handling write errors
If a write error occurs, the affected block is placed on the
bad_used_list. In the case that the write error occured
when writing summary data the block was also being placed on
the dirty_list, which caused list corruption and ultimately
a soft lockup in jffs2_mark_node_obsolete. This fixes that.
Signed-off-by: Adrian Hunter <ext-adrian.hunter at nokia.com>
Signed-off-by: Artem Bityutskiy <Artem.Bityutskiy at nokia.com>
Signed-off-by: David Woodhouse <dwmw2 at infradead.org>
---
fs/jffs2/nodemgmt.c | 5 +++++
1 files changed, 5 insertions(+), 0 deletions(-)
diff --git a/fs/jffs2/nodemgmt.c b/fs/jffs2/nodemgmt.c
index d883769..c8b50de 100644
--- a/fs/jffs2/nodemgmt.c
+++ b/fs/jffs2/nodemgmt.c
@@ -172,6 +172,11 @@ int jffs2_reserve_space_gc(struct jffs2_sb_info *c, uint32_t minsize,
static void jffs2_close_nextblock(struct jffs2_sb_info *c, struct jffs2_eraseblock *jeb)
{
+ if (c->nextblock == NULL) {
+ D1(printk(KERN_DEBUG "jffs2_close_nextblock: Erase block at 0x%08x has already been placed in a list\n",
+ jeb->offset));
+ return;
+ }
/* Check, if we have a dirty block now, or if it was dirty already */
if (ISDIRTY (jeb->wasted_size + jeb->dirty_size)) {
c->dirty_size += jeb->wasted_size;
More information about the linux-mtd-cvs
mailing list