From: Boris Brezillon <boris.brezillon@bootlin.com>
To: OuYang ZhiZhong <oyzhizhong@gmail.com>
Cc: dwmw2@infradead.org, computersforpeace@gmail.com,
boris.brezillon@free-electrons.com, marek.vasut@gmail.com,
richard@nod.at, vdavydov.dev@gmail.com,
cyrille.pitchen@wedev4u.fr, linux-mtd@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mtdchar: fix usage of mtd_ooblayout_ecc()
Date: Mon, 5 Mar 2018 16:32:23 +0100 [thread overview]
Message-ID: <20180305163223.41ae1a6f@bbrezillon> (raw)
In-Reply-To: <1520261626-17395-1-git-send-email-oyzhizhong@gmail.com>
Hi OuYang,
On Mon, 5 Mar 2018 22:53:46 +0800
OuYang ZhiZhong <oyzhizhong@gmail.com> wrote:
> Section was not properly computed. The value of OOB region definition is
> always ECC section 0 information in the OOB area, but we want to get all
> the ECC bytes information, so we should call
> mtd_ooblayout_ecc(mtd, section++, &oobregion) until it returns -ERANGE.
Oops, indeed.
>
> This is fixed by using i instead of section.
>
Fixes: c2b78452a9db ("mtd: use mtd_ooblayout_xxx() helpers where appropriate")
Cc: <stable@vger.kernel.org>
> Signed-off-by: OuYang ZhiZhong <oyzhizhong@gmail.com>
> ---
> drivers/mtd/mtdchar.c | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/mtd/mtdchar.c b/drivers/mtd/mtdchar.c
> index de8c902..0cc929e 100644
> --- a/drivers/mtd/mtdchar.c
> +++ b/drivers/mtd/mtdchar.c
> @@ -468,7 +468,7 @@ static int shrink_ecclayout(struct mtd_info *mtd,
> struct nand_ecclayout_user *to)
> {
> struct mtd_oob_region oobregion;
> - int i, section = 0, ret;
> + int i, ret;
>
> if (!mtd || !to)
> return -EINVAL;
> @@ -479,7 +479,7 @@ static int shrink_ecclayout(struct mtd_info *mtd,
> for (i = 0; i < MTD_MAX_ECCPOS_ENTRIES;) {
> u32 eccpos;
>
> - ret = mtd_ooblayout_ecc(mtd, section, &oobregion);
> + ret = mtd_ooblayout_ecc(mtd, i, &oobregion);
Nope, you're not fixing the problem with that: i is encoding the
->eccpos index, not the OOB section. You should really do section++,
either here, or in the for statement.
> if (ret < 0) {
> if (ret != -ERANGE)
> return ret;
> @@ -515,7 +515,7 @@ static int shrink_ecclayout(struct mtd_info *mtd,
> static int get_oobinfo(struct mtd_info *mtd, struct nand_oobinfo *to)
> {
> struct mtd_oob_region oobregion;
> - int i, section = 0, ret;
> + int i, ret;
>
> if (!mtd || !to)
> return -EINVAL;
> @@ -526,7 +526,7 @@ static int get_oobinfo(struct mtd_info *mtd, struct nand_oobinfo *to)
> for (i = 0; i < ARRAY_SIZE(to->eccpos);) {
> u32 eccpos;
>
> - ret = mtd_ooblayout_ecc(mtd, section, &oobregion);
> + ret = mtd_ooblayout_ecc(mtd, i, &oobregion);
Ditto.
> if (ret < 0) {
> if (ret != -ERANGE)
> return ret;
Thanks,
Boris
--
Boris Brezillon, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2018-03-05 15:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-05 14:53 [PATCH] mtdchar: fix usage of mtd_ooblayout_ecc() OuYang ZhiZhong
2018-03-05 15:32 ` Boris Brezillon [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=20180305163223.41ae1a6f@bbrezillon \
--to=boris.brezillon@bootlin.com \
--cc=boris.brezillon@free-electrons.com \
--cc=computersforpeace@gmail.com \
--cc=cyrille.pitchen@wedev4u.fr \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=marek.vasut@gmail.com \
--cc=oyzhizhong@gmail.com \
--cc=richard@nod.at \
--cc=vdavydov.dev@gmail.com \
/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