From: Zhihao Cheng <chengzhihao1@huawei.com>
To: Wang YanQing <udknight@gmail.com>, <richard@nod.at>,
<miquel.raynal@bootlin.com>, <bbrezillon@kernel.org>,
<vigneshr@ti.com>, <linux-mtd@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] mtd: ubi: eba.c: fix return value overwrite issue in try_write_vid_and_data()
Date: Wed, 29 Mar 2023 09:14:17 +0800 [thread overview]
Message-ID: <8f312163-f809-9271-3f1d-792d23d1bdfa@huawei.com> (raw)
In-Reply-To: <20230328153534.GA12409@udknight>
> 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>
> ---
> Changes v1-v2:
> 1: add error code in warning message, suggested by Zhihao Cheng
>
> drivers/mtd/ubi/eba.c | 19 ++++++++++++++-----
> 1 file changed, 14 insertions(+), 5 deletions(-)
>
Reviewed-by: Zhihao Cheng <chengzhihao1@huawei.com>
> diff --git a/drivers/mtd/ubi/eba.c b/drivers/mtd/ubi/eba.c
> index 09c408c..4e1d807 100644
> --- a/drivers/mtd/ubi/eba.c
> +++ b/drivers/mtd/ubi/eba.c
> @@ -946,7 +946,7 @@ static int try_write_vid_and_data(struct ubi_volume *vol, int lnum,
> int offset, int len)
> {
> struct ubi_device *ubi = vol->ubi;
> - int pnum, opnum, err, vol_id = vol->vol_id;
> + int pnum, opnum, err, err2, vol_id = vol->vol_id;
>
> pnum = ubi_wl_get_peb(ubi);
> if (pnum < 0) {
> @@ -981,10 +981,19 @@ 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) {
> + err2 = ubi_wl_put_peb(ubi, vol_id, lnum, pnum, 1);
> + if (err2) {
> + ubi_warn(ubi, "failed to return physical eraseblock %d, error %d",
> + pnum, err2);
> + }
> + } else if (!err && opnum >= 0) {
> + err2 = ubi_wl_put_peb(ubi, vol_id, lnum, opnum, 0);
> + if (err2) {
> + ubi_warn(ubi, "failed to return physical eraseblock %d, error %d",
> + opnum, err2);
> + }
> + }
>
> return err;
> }
>
prev parent reply other threads:[~2023-03-29 1:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-28 15:35 Wang YanQing
2023-03-29 1:14 ` 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=8f312163-f809-9271-3f1d-792d23d1bdfa@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
all inboxes | Powered by JetHome®