From: Zhihao Cheng <chengzhihao1@huawei.com>
To: Wang YanQing <udknight@gmail.com>, <miquel.raynal@bootlin.com>,
<bbrezillon@kernel.org>, <richard@nod.at>, <vigneshr@ti.com>,
<linux-mtd@lists.infradead.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] mtd: ubi: eba.c: fix return value overwrite issue in try_write_vid_and_data()
Date: Mon, 20 Mar 2023 10:44:51 +0800 [thread overview]
Message-ID: <8fbae9fa-f61b-e951-6a13-0629e458c48e@huawei.com> (raw)
In-Reply-To: <20230217165442.GA28288@udknight>
Good catch. Maybe many of history happened unconsistent ubifs images
have related to this point. One small nit below.
> The commit 2d78aee426d8 ("UBI: simplify LEB write and atomic LEB change code")
> adds helper function, try_write_vid_and_data(), to simplify the code, but this
> helper function has bug, it will return 0 (success) when ubi_io_write_vid_hdr()
> or the ubi_io_write_data() return error number (-EIO, etc), because the return
> value of ubi_wl_put_peb() will overwrite the original return value.
>
> This issue will cause unexpected data loss issue, because the caller of this
> function and UBIFS willn't know the data is lost.
>
> Fixes: 2d78aee426d8 ("UBI: simplify LEB write and atomic LEB change code")
>
> Signed-off-by: Wang YanQing <udknight@gmail.com>
> ---
> drivers/mtd/ubi/eba.c | 15 +++++++++++----
> 1 file changed, 11 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/mtd/ubi/eba.c b/drivers/mtd/ubi/eba.c
> index 09c408c..4e32b25 100644
> --- a/drivers/mtd/ubi/eba.c
> +++ b/drivers/mtd/ubi/eba.c
> @@ -981,10 +981,17 @@ static int try_write_vid_and_data(struct ubi_volume *vol, int lnum,
> out_put:
> up_read(&ubi->fm_eba_sem);
>
> - if (err && pnum >= 0)
> - err = ubi_wl_put_peb(ubi, vol_id, lnum, pnum, 1);
> - else if (!err && opnum >= 0)
> - err = ubi_wl_put_peb(ubi, vol_id, lnum, opnum, 0);
> + if (err && pnum >= 0) {
> + if (ubi_wl_put_peb(ubi, vol_id, lnum, pnum, 1) != 0) {
Could we also add error code returned from ubi_wl_put_peb() in warning
message? Same with next ubifs_warn.
> + ubi_warn(ubi, "failed to return physical eraseblock %d",
> + pnum);
> + }
> + } else if (!err && opnum >= 0) {
> + if (ubi_wl_put_peb(ubi, vol_id, lnum, opnum, 0) != 0) {
> + ubi_warn(ubi, "failed to return physical eraseblock %d",
> + opnum);
> + }
> + }
>
> return err;
> }
>
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
prev parent reply other threads:[~2023-03-20 2:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-17 16:58 [PATCH] mtd: ubi: eba.c: fix return value overwrite issue in try_write_vid_and_data() Wang YanQing
2023-02-26 14:14 ` Wang YanQing
2023-02-26 15:52 ` Richard Weinberger
2023-03-20 2:44 ` Zhihao Cheng [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=8fbae9fa-f61b-e951-6a13-0629e458c48e@huawei.com \
--to=chengzhihao1@huawei.com \
--cc=bbrezillon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=miquel.raynal@bootlin.com \
--cc=richard@nod.at \
--cc=udknight@gmail.com \
--cc=vigneshr@ti.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