From: Artem Bityutskiy <dedekind1@gmail.com>
To: Holger Brunck <holger.brunck@keymile.com>
Cc: "Walter, Axel" <Axel.Walter@keymile.com>,
linux-mtd@lists.infradead.org, Detlev Zundel <dzu@denx.de>
Subject: Re: UBI: corrupted PEB detection for Numonyx P30
Date: Tue, 25 Jan 2011 13:11:54 +0200 [thread overview]
Message-ID: <1295953914.7118.11.camel@localhost> (raw)
In-Reply-To: <4D3D7AB5.50401@keymile.com>
On Mon, 2011-01-24 at 14:12 +0100, Holger Brunck wrote:
> err1 = ubi_io_read_vid_hdr(ubi, pnum, &vid_hdr, 0);
> - if (err1 == UBI_IO_BAD_HDR_EBADMSG || err1 == UBI_IO_BAD_HDR) {
> + if (err1 == UBI_IO_BAD_HDR_EBADMSG || err1 == UBI_IO_BAD_HDR ||
> + err1 == UBI_IO_FF || err1 == UBI_IO_FF_BITFLIPS) {
> struct ubi_ec_hdr ec_hdr;
>
> err1 = ubi_io_read_ec_hdr(ubi, pnum, &ec_hdr, 0);
> - if (err1 == UBI_IO_BAD_HDR_EBADMSG || err1 == UBI_IO_BAD_HDR)
> + if (err1 == UBI_IO_BAD_HDR_EBADMSG || err1 == UBI_IO_BAD_HDR ||
> + err1 == UBI_IO_FF || err1 == UBI_IO_FF_BITFLIPS) {
> /*
> * Both VID and EC headers are corrupted, so we can
> * safely erase this PEB and not afraid that it will be
>
> Does anyone see a problem with this patch? If not I can post it as a git patch
> on the mailing list.
Hi, I agree with checking for UBI_IO_FF, but not for UBI_IO_FF_BITFLIPS,
because (a) NOR should not have them and (b) bit-flip means the the
header is correct, but there was a correctable bit-blip. But we want to
find the headers corrupted in this piece of code.
I've prepared and pushed almost the same patch, made you the author:
http://git.infradead.org/ubi-2.6.git/commit/4782254b5f76c22726d270ea753816cefa088ae9
Please, take a look and check. If you do not like it, let me know or
just send the patch you like.
Thanks!
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
next prev parent reply other threads:[~2011-01-25 11:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-24 13:12 UBI: corrupted PEB detection for Numonyx P30 Holger Brunck
2011-01-25 11:11 ` Artem Bityutskiy [this message]
2011-01-25 11:31 ` Holger Brunck
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=1295953914.7118.11.camel@localhost \
--to=dedekind1@gmail.com \
--cc=Axel.Walter@keymile.com \
--cc=dzu@denx.de \
--cc=holger.brunck@keymile.com \
--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.