From: boris.brezillon@free-electrons.com (Boris Brezillon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] mtd: nand: mxc: Fix mxc_v1 ooblayout
Date: Fri, 25 Nov 2016 11:27:25 +0100 [thread overview]
Message-ID: <20161125112725.0ee9d49d@bbrezillon> (raw)
In-Reply-To: <58eed307-ee50-9727-7b64-891d1b969790@gmail.com>
On Fri, 25 Nov 2016 10:58:26 +0100
Marek Vasut <marek.vasut@gmail.com> wrote:
> On 11/25/2016 10:13 AM, Boris Brezillon wrote:
> > Commit a894cf6c5a82 ("mtd: nand: mxc: switch to mtd_ooblayout_ops")
> > introduced a bug in the OOB layout description. Even if the driver claims
> > that 3 ECC bytes are reserved to protect 512 bytes of data, it's actually
> > 5 ECC bytes to protect 512+6 bytes of data (some OOB bytes are also
> > protected using extra ECC bytes).
> >
> > Fix the mxc_v1_ooblayout_{free,ecc}() functions to reflect this behavior.
> >
> > Signed-off-by: Boris Brezillon <boris.brezillon@free-electrons.com>
> > Fixes: a894cf6c5a82 ("mtd: nand: mxc: switch to mtd_ooblayout_ops")
> > Cc: <stable@vger.kernel.org>
> > ---
> > drivers/mtd/nand/mxc_nand.c | 5 ++---
> > 1 file changed, 2 insertions(+), 3 deletions(-)
> >
> > diff --git a/drivers/mtd/nand/mxc_nand.c b/drivers/mtd/nand/mxc_nand.c
> > index 61ca020c5272..c19ec4f0983e 100644
> > --- a/drivers/mtd/nand/mxc_nand.c
> > +++ b/drivers/mtd/nand/mxc_nand.c
> > @@ -886,7 +886,7 @@ static int mxc_v1_ooblayout_ecc(struct mtd_info *mtd, int section,
> > return -ERANGE;
> >
> > oobregion->offset = (section * 16) + 6;
> > - oobregion->length = nand_chip->ecc.bytes;
> > + oobregion->length = 5;
>
> Use a macro instead of hard-coding a value please :)
Ideally, we should change ->eccbytes value in the
imx27_nand_devtype_data and imx21_nand_devtype_data definitions, but I
fear it could break other things.
I'll define a macro.
>
> > return 0;
> > }
> > @@ -908,8 +908,7 @@ static int mxc_v1_ooblayout_free(struct mtd_info *mtd, int section,
> > oobregion->length = 4;
> > }
> > } else {
> > - oobregion->offset = ((section - 1) * 16) +
> > - nand_chip->ecc.bytes + 6;
> > + oobregion->offset = ((section - 1) * 16) + 5 + 6;
>
> DTTO here, the math here is cryptic enough.
>
> > if (section < nand_chip->ecc.steps)
> > oobregion->length = (section * 16) + 6 -
> > oobregion->offset;
> >
>
>
next prev parent reply other threads:[~2016-11-25 10:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-25 9:13 [PATCH] mtd: nand: mxc: Fix mxc_v1 ooblayout Boris Brezillon
2016-11-25 9:58 ` Marek Vasut
2016-11-25 10:27 ` Boris Brezillon [this message]
2016-11-25 10:40 ` Marek Vasut
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=20161125112725.0ee9d49d@bbrezillon \
--to=boris.brezillon@free-electrons.com \
--cc=linux-arm-kernel@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;
as well as URLs for NNTP newsgroup(s).