From: Shmulik Ladkani <shmulik.ladkani@gmail.com>
To: David Woodhouse <dwmw2@infradead.org>,
Artem Bityutskiy <artem.bityutskiy@linux.intel.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: [PATCH] mtd: nand: Properly initialize 'mtd->bitflip_threshold' prior 'scan_bbt()' is invoked
Date: Fri, 8 Jun 2012 19:17:41 +0300 [thread overview]
Message-ID: <20120608191741.3877cd3a@halley> (raw)
In-Reply-To: <20120608182906.57b4844a@halley>
Artem, David,
Patch was accidentally submitted twice.
Disregard this post please.
Sorry for the inconvenience.
Regards,
Shmulik
On Fri, 8 Jun 2012 18:29:06 +0300 Shmulik Ladkani <shmulik@jungo.com> wrote:
> As of edbc454 [mtd: driver _read() returns max_bitflips; mtd_read()
> returns -EUCLEAN], 'mtd->bitflip_threshold' must be set for mtd devices
> having ECC, prior any 'mtd_read()' call.
> Otherwise, 'mtd_read()' will falsely return -EUCLEAN.
>
> Normally, 'mtd->bitflip_threshold' is initialized when the MTD is added.
>
> However, this is too late for NAND MTDs, as 'scan_bbt()' is invoked
> prior the existing initialization of 'mtd->bitflip_threshold'.
>
> This is a problem since 'scan_bbt()' calls 'mtd_read()', in the case
> of a flash-based bad block table.
> It resulted in a falsely reported bitflips indication during BBT read,
> which lead to constant scrubbing of the flash BBT blocks.
>
> Initialize 'mtd->bitflip_threshold' to its default value (if not already
> set by the driver), prior invocation of 'scan_bbt()'.
>
> Reported-by: Sascha Hauer <s.hauer@pengutronix.de>
> Signed-off-by: Shmulik Ladkani <shmulik.ladkani@gmail.com>
next prev parent reply other threads:[~2012-06-08 16:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-08 15:29 [PATCH] mtd: nand: Properly initialize 'mtd->bitflip_threshold' prior 'scan_bbt()' is invoked Shmulik Ladkani
2012-06-08 15:29 ` Shmulik Ladkani
2012-06-08 16:17 ` Shmulik Ladkani [this message]
2012-06-08 17:12 ` Artem Bityutskiy
2012-06-08 17:12 ` Artem Bityutskiy
2012-06-09 9:43 ` Sascha Hauer
2012-06-09 9:43 ` Sascha Hauer
2012-06-09 11:03 ` David Woodhouse
2012-06-09 11:03 ` David Woodhouse
2012-06-09 15:47 ` Mike Dunn
2012-06-09 15:47 ` Mike Dunn
-- strict thread matches above, loose matches on Subject: below --
2012-06-08 15:41 Shmulik Ladkani
2012-06-08 15:41 ` Shmulik Ladkani
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=20120608191741.3877cd3a@halley \
--to=shmulik.ladkani@gmail.com \
--cc=artem.bityutskiy@linux.intel.com \
--cc=dwmw2@infradead.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.