From: Artem Bityutskiy <dedekind1@gmail.com>
To: Brian Norris <computersforpeace@gmail.com>
Cc: David Woodhouse <dwmw2@infradead.org>,
Jim Quinlan <jim2101024@gmail.com>,
linux-mtd@lists.infradead.org,
Kevin Cernekee <cernekee@gmail.com>
Subject: Re: [PATCH 0/3] fixups for OOB ECC problems
Date: Wed, 29 Jun 2011 09:59:04 +0300 [thread overview]
Message-ID: <1309330748.23597.125.camel@sauron> (raw)
In-Reply-To: <1309303740-9936-1-git-send-email-computersforpeace@gmail.com>
On Tue, 2011-06-28 at 16:28 -0700, Brian Norris wrote:
> Hello,
>
> Now that we have added the possibility that mtd->read_oob returns
> -EUCLEAN or -EBADMSG for corrected bitflips and for uncorrectable errors,
> respectively, there are more pieces of code that need to take this into
> account. These patches should address some of these by ignoring bitflips
> when bit accuracy is not needed or by ignoring corrected errors when
> scrubbing would be unnecessary.
>
> There are still other cases to address, for example, some flash-based BBT
> code.
>
> This applies on top of l2-mtd-2.6.git. Patch 3 is an amendment to commit
> abf386c475beab813dc9b3366e592e00255e987a, ("mtd: nand: handle ECC errors
> in OOB"), so it can be squashed in if you want. Let me know if you want
> me to do this and do a resend.
Do you test these things somehow? I'd just injected some code to a
driver or nandsim which returns -EUCLEAN for OOB and check what fails.
--
Best Regards,
Artem Bityutskiy
next prev parent reply other threads:[~2011-06-29 6:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-28 23:28 [PATCH 0/3] fixups for OOB ECC problems Brian Norris
2011-06-28 23:28 ` [PATCH 1/3] mtd: nand: ignore ECC errors for simple BBM scans Brian Norris
2011-06-29 7:02 ` Artem Bityutskiy
2011-06-28 23:28 ` [PATCH 2/3] mtd: tests: ignore corrected bitflips in OOB on mtd_readtest Brian Norris
2011-06-28 23:29 ` [PATCH 3/3] mtd: edit NAND-related comment Brian Norris
2011-06-29 6:59 ` Artem Bityutskiy [this message]
2011-06-29 20:24 ` [PATCH 0/3] fixups for OOB ECC problems Brian Norris
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=1309330748.23597.125.camel@sauron \
--to=dedekind1@gmail.com \
--cc=cernekee@gmail.com \
--cc=computersforpeace@gmail.com \
--cc=dwmw2@infradead.org \
--cc=jim2101024@gmail.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.