All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Weinberger <richard@nod.at>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: linux-mtd@lists.infradead.org, kernel@pengutronix.de,
	Han Xu <han.xu@nxp.com>,
	Boris Brezillon <boris.brezillon@free-electrons.com>
Subject: Re: [PATCH] mtd: nand: gpmi: Fix failure when a erased page has a bitflip at BBM
Date: Tue, 05 Dec 2017 19:40:54 +0100	[thread overview]
Message-ID: <2221916.oFKidPPRfi@blindfold> (raw)
In-Reply-To: <20171205105140.915-1-s.hauer@pengutronix.de>

Am Dienstag, 5. Dezember 2017, 11:51:40 CET schrieb Sascha Hauer:
> When erased subpages are read then the BCH decoder returns STATUS_ERASED
> if they are all empty, or STATUS_UNCORRECTABLE if there are bitflips.
> When there are bitflips, we have to set these bits again to show the
> upper layers a completely erased page. When a bitflip happens in the
> exact byte where the bad block marker is, then this byte is swapped
> with another byte in block_mark_swapping(). The correction code then
> detects a bitflip in another subpage and no longer corrects the bitflip
> where it really happens.
> 
> Correct this behaviour by calling block_mark_swapping() after the
> bitflips have been corrected.
> 
> In our case UBIFS failed with this bug because it expects erased
> pages to be really empty:
> 
> UBIFS error (pid 187): ubifs_scan: corrupt empty space at LEB 36:118735
> UBIFS error (pid 187): ubifs_scanned_corruption: corruption at LEB 36:118735
> UBIFS error (pid 187): ubifs_scanned_corruption: first 8192 bytes from LEB
> 36:118735 UBIFS error (pid 187): ubifs_scan: LEB 36 scanning failed
> UBIFS error (pid 187): do_commit: commit failed, error -117
> 
> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
> ---
>  drivers/mtd/nand/gpmi-nand/gpmi-nand.c | 6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/drivers/mtd/nand/gpmi-nand/gpmi-nand.c
> b/drivers/mtd/nand/gpmi-nand/gpmi-nand.c index 50f8d4a1b983..d4d824ef64e9
> 100644
> --- a/drivers/mtd/nand/gpmi-nand/gpmi-nand.c
> +++ b/drivers/mtd/nand/gpmi-nand/gpmi-nand.c
> @@ -1067,9 +1067,6 @@ static int gpmi_ecc_read_page(struct mtd_info *mtd,
> struct nand_chip *chip, return ret;
>  	}
> 
> -	/* handle the block mark swapping */
> -	block_mark_swapping(this, payload_virt, auxiliary_virt);
> -
>  	/* Loop over status bytes, accumulating ECC status. */
>  	status = auxiliary_virt + nfc_geo->auxiliary_status_offset;
> 
> @@ -1158,6 +1155,9 @@ static int gpmi_ecc_read_page(struct mtd_info *mtd,
> struct nand_chip *chip, max_bitflips = max_t(unsigned int, max_bitflips,
> *status);
>  	}
> 
> +	/* handle the block mark swapping */
> +	block_mark_swapping(this, buf, auxiliary_virt);
> +
>  	if (oob_required) {
>  		/*
>  		 * It's time to deliver the OOB bytes. See gpmi_ecc_read_oob()

Fixes: bd2e778c9ee3 ("gpmi-nand: Handle ECC Errors in erased pages")
Reviewed-by: Richard Weinberger <richard@nod.at>

Thanks,
//richard

  reply	other threads:[~2017-12-05 18:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-05 10:51 [PATCH] mtd: nand: gpmi: Fix failure when a erased page has a bitflip at BBM Sascha Hauer
2017-12-05 18:40 ` Richard Weinberger [this message]
2017-12-06  9:14   ` Boris Brezillon

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=2221916.oFKidPPRfi@blindfold \
    --to=richard@nod.at \
    --cc=boris.brezillon@free-electrons.com \
    --cc=han.xu@nxp.com \
    --cc=kernel@pengutronix.de \
    --cc=linux-mtd@lists.infradead.org \
    --cc=s.hauer@pengutronix.de \
    /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.