From: Artem Bityutskiy <dedekind1@gmail.com>
To: Sankara Narayanan Balasubramanian <sankara.narayanan@tridentmicro.com>
Cc: Somashekar Umadi <Somashekar.Umadi@tridentmicro.com>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: JFFS2_WBUF_VERIFY patch clarification (RESENT)
Date: Thu, 31 Mar 2011 17:34:14 +0300 [thread overview]
Message-ID: <1301582054.2828.95.camel@localhost> (raw)
In-Reply-To: <C7C7E27CD4B28D47A856D6DA52BA5D9E8E5D8260@eu-exh-02.EU.TRID.COM>
On Wed, 2011-03-23 at 05:40 +0000, Sankara Narayanan Balasubramanian
wrote:
> Hi,
>
> We are using JFFS2 as part of our linux kernel v2.6.18 in our product.
> We are using JFFS2 file system on top of the MTD Driver for NAND Flash
> (SLC Nand flash). We observe the problem during our long duration file
> write tests (endurance tests) that occasionally the data written
> through the fwrite function call is not present in the flash.
>
> We checked the latest kernel sources (2.6.37) and observed a similar
> problem being resolved through the JFFS2_WBUF_VERIFY patch. We took
> only that patch (implementation into our wbuf.c file) and we observe
> that the problem is resolved. We request you to provide the feedback
> for the following.
>
> 1. Can this patch be taken as a stand-alone patch into our existing
> JFFS2 as part of linux 2.6.18 release
No, this release is not supported by anyone anymore. I think the oldest
long-term stable kernel is 2.6.27.
> 2. What is the exact behavior of the patch? We observe that the patch
> ensures that the jffs2_wbuf_recovery is called once more if the first
> attempt to verify fails. How does it ensure that the data is written
> into the flash properly?
Which patch? Specify commit id or send it.
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
prev parent reply other threads:[~2011-03-31 14:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-23 5:40 JFFS2_WBUF_VERIFY patch clarification (RESENT) Sankara Narayanan Balasubramanian
2011-03-31 14:34 ` Artem Bityutskiy [this message]
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=1301582054.2828.95.camel@localhost \
--to=dedekind1@gmail.com \
--cc=Somashekar.Umadi@tridentmicro.com \
--cc=linux-mtd@lists.infradead.org \
--cc=sankara.narayanan@tridentmicro.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.