All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthieu CASTET <matthieu.castet@parrot.com>
To: Iwo Mergler <iwo@call-direct.com.au>
Cc: dwmw2@infradead.org, joern@logfs.org,
	linux-mtd@lists.infradead.org,
	Alexey Korolev <akorolev@infradead.org>
Subject: Re: [BUG] JFFS2 power loss recovery issues on NAND
Date: Tue, 17 Jun 2008 10:13:06 +0200	[thread overview]
Message-ID: <48577212.9070004@parrot.com> (raw)
In-Reply-To: <48570D5A.1050906@call-direct.com.au>

Iwo Mergler wrote:
> Alexey Korolev wrote:
>>   
> Alexey,
> 
> I know of at least one hardware ECC implementation which can flag
> errors within the ECC bytes separately. In other words, not all 
> implementations
> will detect/correct bit errors in the case of a ECC write error.
> 
> About how to fix it - what about making the reading without ECC the default
> and only re-reading with ECC if JFFS2 finds an invalid checksum?
> 
But what happen if a but flip happen ?
If we do this, ecc won't correct it, the error can happen everywhere not 
only in checksum, for example wrong nodetype.

If only we could put a marker after the ecc data, we could detect such 
case. But linux put ecc at the end of oob.

Matthieu

  reply	other threads:[~2008-06-17  8:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-10 13:57 [BUG] JFFS2 power loss recovery issues on NAND Alexey Korolev
2008-06-17  1:03 ` Iwo Mergler
2008-06-17  8:13   ` Matthieu CASTET [this message]
2008-06-17  9:24     ` Jörn Engel
2008-06-17 16:00       ` Alexey Korolev
2008-06-17 16:57         ` Jörn Engel
2008-06-17 23:51     ` Iwo Mergler
2008-06-18 12:19       ` Jamie Lokier
2008-06-18 12:33         ` David Woodhouse

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=48577212.9070004@parrot.com \
    --to=matthieu.castet@parrot.com \
    --cc=akorolev@infradead.org \
    --cc=dwmw2@infradead.org \
    --cc=iwo@call-direct.com.au \
    --cc=joern@logfs.org \
    --cc=linux-mtd@lists.infradead.org \
    /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.