mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Zhihao Cheng <chengzhihao1@huawei.com>
To: Qingfang Deng <dqfext@gmail.com>,
	David Woodhouse <dwmw2@infradead.org>,
	Richard Weinberger <richard@nod.at>,
	Qingfang Deng <qingfang.deng@siflower.com.cn>,
	<linux-mtd@lists.infradead.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] jffs2: fix use of uninitialized variable
Date: Mon, 1 Jul 2024 14:33:45 +0800	[thread overview]
Message-ID: <587f2211-8667-ff30-db5b-8b6e3f61a15d@huawei.com> (raw)
In-Reply-To: <20240701045206.162103-1-dqfext@gmail.com>

在 2024/7/1 12:52, Qingfang Deng 写道:
> From: Qingfang Deng <qingfang.deng@siflower.com.cn>
> 
> When building the kernel with -Wmaybe-uninitialized, the compiler
> reports this warning:
> 
> In function 'jffs2_mark_erased_block',
>      inlined from 'jffs2_erase_pending_blocks' at fs/jffs2/erase.c:116:4:
> fs/jffs2/erase.c:474:9: warning: 'bad_offset' may be used uninitialized [-Wmaybe-uninitialized]
>    474 |         jffs2_erase_failed(c, jeb, bad_offset);
>        |         ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> fs/jffs2/erase.c: In function 'jffs2_erase_pending_blocks':
> fs/jffs2/erase.c:402:18: note: 'bad_offset' was declared here
>    402 |         uint32_t bad_offset;
>        |                  ^~~~~~~~~~
> 
> When mtd->point() is used, jffs2_erase_pending_blocks can return -EIO
> without initializing bad_offset, which is later used at the filebad
> label in jffs2_mark_erased_block.
> Fix it by initializing this variable.
> 
> Fixes: 8a0f572397ca ("[JFFS2] Return values of jffs2_block_check_erase error paths")
> Signed-off-by: Qingfang Deng <qingfang.deng@siflower.com.cn>
> ---
>   fs/jffs2/erase.c | 7 +++----
>   1 file changed, 3 insertions(+), 4 deletions(-)
> 
Reviewed-by: Zhihao Cheng <chengzhihao1@huawei.com>
> diff --git a/fs/jffs2/erase.c b/fs/jffs2/erase.c
> index acd32f05b519..ef3a1e1b6cb0 100644
> --- a/fs/jffs2/erase.c
> +++ b/fs/jffs2/erase.c
> @@ -338,10 +338,9 @@ static int jffs2_block_check_erase(struct jffs2_sb_info *c, struct jffs2_erasebl
>   		} while(--retlen);
>   		mtd_unpoint(c->mtd, jeb->offset, c->sector_size);
>   		if (retlen) {
> -			pr_warn("Newly-erased block contained word 0x%lx at offset 0x%08tx\n",
> -				*wordebuf,
> -				jeb->offset +
> -				c->sector_size-retlen * sizeof(*wordebuf));
> +			*bad_offset = jeb->offset + c->sector_size - retlen * sizeof(*wordebuf);
> +			pr_warn("Newly-erased block contained word 0x%lx at offset 0x%08x\n",
> +				*wordebuf, *bad_offset);
>   			return -EIO;
>   		}
>   		return 0;
> 


  reply	other threads:[~2024-07-01  6:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-01  4:52 Qingfang Deng
2024-07-01  6:33 ` Zhihao Cheng [this message]
2024-11-12  5:46 ` Qingfang Deng
2024-11-12  6:59   ` Richard Weinberger

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=587f2211-8667-ff30-db5b-8b6e3f61a15d@huawei.com \
    --to=chengzhihao1@huawei.com \
    --cc=dqfext@gmail.com \
    --cc=dwmw2@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=qingfang.deng@siflower.com.cn \
    --cc=richard@nod.at \
    /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®