From: Artem Bityutskiy <dedekind1@gmail.com>
To: Matthieu CASTET <matthieu.castet@parrot.com>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: bbt and bitflip
Date: Fri, 22 Apr 2011 11:08:05 +0300 [thread overview]
Message-ID: <1303459685.2757.42.camel@localhost> (raw)
In-Reply-To: <4DB033E4.6030105@parrot.com>
Matthieu,
nice finding.
On Thu, 2011-04-21 at 15:40 +0200, Matthieu CASTET wrote:
> Hi,
>
> the current bad block table implementation doesn't seem robust against bit flip.
>
> at boot we call :
> - search_read_bbts which scan for bbt using oob pattern.
> - check_create
> -- read_abs_bbt
> --- read_bbt which ignore ecc bit flip/error
>
> So if bit flip happen in BBT, we never scrub it.
This should probably be fixed.
> And if bit flip accumulate and we can't correct it anymore, the code will parse
> the corrupted data and our bad block info will be wrong (valid block can be
> marked as bad and we lose bad, bad block can be see as valid).
The bbt should be protected with CRC and if it gets corrupted we should
re-scan the flash and re-create it.
> Also the pattern and version in oob isn't protected by ecc. They can be corrupted.
>
> Are bbt safe to use ?
It does not look like.
> Are there any plan to make the bbt more robust ?
I would guess no unless you do it :-)
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
prev parent reply other threads:[~2011-04-22 8:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-21 13:40 bbt and bitflip Matthieu CASTET
2011-04-21 17:17 ` Matthieu CASTET
2011-04-22 8:14 ` Artem Bityutskiy
2011-04-22 8:15 ` Artem Bityutskiy
2011-06-23 16:36 ` Brian Norris
2011-06-24 19:55 ` Artem Bityutskiy
2011-06-24 20:36 ` Matthew L. Creech
2011-04-22 8:08 ` 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=1303459685.2757.42.camel@localhost \
--to=dedekind1@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=matthieu.castet@parrot.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.