Linux-mtd Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Brian Norris <computersforpeace@gmail.com>
To: Huang Shijie <b32955@freescale.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: [PATCH v2] mtd: nand: fix off-by-one read retry mode counting
Date: Fri, 14 Feb 2014 12:15:57 -0800	[thread overview]
Message-ID: <20140214201557.GQ18440@ld-irv-0074> (raw)
In-Reply-To: <20140214075820.GC22570@shlinux2.ap.freescale.net>

On Fri, Feb 14, 2014 at 03:58:21PM +0800, Huang Shijie wrote:
> On Wed, Feb 12, 2014 at 05:22:11PM -0800, Brian Norris wrote:
> > A flash may support N read retry voltage threshold modes, numbered 1
> > through N-1 (where mode 0 represents the initial state). However,
> > nand_do_read_ops() tries to use mode 0 through N.
> > 
> > This off-by-one error shows up, for instance, when using nanddump, and
> > we have cycled through available modes:
> > 
> >     nand: setting READ RETRY mode 0
> >     nand: setting READ RETRY mode 1
> >     nand: setting READ RETRY mode 2
> >     nand: setting READ RETRY mode 3
> >     nand: setting READ RETRY mode 4
> >     nand: setting READ RETRY mode 5
> >     nand: setting READ RETRY mode 6
> >     nand: setting READ RETRY mode 7
> >     nand: setting READ RETRY mode 8
> >     libmtd: error!: cannot read 8192 bytes from mtd0 (eraseblock 20, offset 0)
> >             error 22 (Invalid argument)
> >     nanddump: error!: mtd_read
> > 
> > Tested on Micron MT29F64G08CBCBBH1, with 8 retry modes.
> > 
> > Signed-off-by: Brian Norris <computersforpeace@gmail.com>
> > ---
> > v1 -> v2: N modes means we should use modes 0 to N-1, not 0 to N
> > 
> >  drivers/mtd/nand/nand_base.c | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> > 
> > diff --git a/drivers/mtd/nand/nand_base.c b/drivers/mtd/nand/nand_base.c
> > index 9be7842f300e..3cb1cefcd926 100644
> > --- a/drivers/mtd/nand/nand_base.c
> > +++ b/drivers/mtd/nand/nand_base.c
> > @@ -1586,7 +1586,7 @@ read_retry:
> >  			}
> >  
> >  			if (mtd->ecc_stats.failed - ecc_failures) {
> > -				if (retry_mode + 1 <= chip->read_retries) {
> > +				if (retry_mode + 1 < chip->read_retries) {
> >  					retry_mode++;
> >  					ret = nand_setup_read_retry(mtd,
> >  							retry_mode);
> 
> Acked-by: Huang Shijie <b32955@freescale.com>

Pushed to linux-mtd.git. Will queue up a few other things to send to
Linus in 3.14-rcX.

Brian

      reply	other threads:[~2014-02-14 20:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-13  1:22 [PATCH v2] mtd: nand: fix off-by-one read retry mode counting Brian Norris
2014-02-14  7:58 ` Huang Shijie
2014-02-14 20:15   ` Brian Norris [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=20140214201557.GQ18440@ld-irv-0074 \
    --to=computersforpeace@gmail.com \
    --cc=b32955@freescale.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox