From: Richard Purdie <rpurdie@rpsys.net>
To: Josh Boyer <jwboyer@gmail.com>, Greg KH <greg@kroah.com>
Cc: David Woodhouse <dwmw2@infradead.org>,
linux-mtd <linux-mtd@lists.infradead.org>,
Thomas Gleixner <tglx@linutronix.de>,
LKML <linux-kernel@vger.kernel.org>
Subject: [PATCH] [MTD] Protect chip->ops with correct locking - fix jffs2 corruption
Date: Mon, 21 Aug 2006 10:05:10 +0100 [thread overview]
Message-ID: <1156151110.5557.33.camel@localhost.localdomain> (raw)
Read the return value before we release the nand device otherwise the
value can become corrupted by another user of chip->ops, ultimately
resulting in filesystem corruption.
Signed-off-by: Richard Purdie <rpurdie@rpsys.net>
Acked-by: Josh Boyer <jwboyer@gmail.com>
---
This fixes the jffs2 errors and filesystem corruption I reported. It
should be applied for 2.6.18.
On Sun, 2006-08-20 at 18:35 -0700, Greg KH wrote:
> On Sat, Aug 19, 2006 at 08:34:46PM -0500, Josh Boyer wrote:
> > We have multiple confirmations that this patch fixes the issue
> > reported. I agree it should go in 2.6.18.
> >
> > Greg, can you add this to your tree?
>
> Add what to what tree? I need things to be a bit more specific
> here :)
drivers/mtd/nand/nand_base.c | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
Index: git/drivers/mtd/nand/nand_base.c
===================================================================
--- git.orig/drivers/mtd/nand/nand_base.c 2006-08-17 22:46:19.000000000 +0100
+++ git/drivers/mtd/nand/nand_base.c 2006-08-17 22:47:27.000000000 +0100
@@ -1093,9 +1093,10 @@ static int nand_read(struct mtd_info *mt
ret = nand_do_read_ops(mtd, from, &chip->ops);
+ *retlen = chip->ops.retlen;
+
nand_release_device(mtd);
- *retlen = chip->ops.retlen;
return ret;
}
@@ -1691,9 +1692,10 @@ static int nand_write(struct mtd_info *m
ret = nand_do_write_ops(mtd, to, &chip->ops);
+ *retlen = chip->ops.retlen;
+
nand_release_device(mtd);
- *retlen = chip->ops.retlen;
return ret;
}
reply other threads:[~2006-08-21 9:08 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1156151110.5557.33.camel@localhost.localdomain \
--to=rpurdie@rpsys.net \
--cc=dwmw2@infradead.org \
--cc=greg@kroah.com \
--cc=jwboyer@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®