From: Gao Xiang <hsiangkao@redhat.com>
To: Joe Perches <joe@perches.com>
Cc: Colin King <colin.king@canonical.com>,
Gao Xiang <xiang@kernel.org>, Chao Yu <chao@kernel.org>,
linux-erofs@lists.ozlabs.org, kernel-janitors@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH][next] erofs: fix uninitialized variable i used in a while-loop
Date: Wed, 7 Apr 2021 11:51:07 +0800 [thread overview]
Message-ID: <20210407035107.GA239118@xiangao.remote.csb> (raw)
In-Reply-To: <b56a44542a338583279893870ec819d4b1b4e23b.camel@perches.com>
Hi Joe,
On Tue, Apr 06, 2021 at 08:38:44PM -0700, Joe Perches wrote:
> On Wed, 2021-04-07 at 07:54 +0800, Gao Xiang wrote:
> > Hi Colin,
> >
> > On Tue, Apr 06, 2021 at 05:27:18PM +0100, Colin King wrote:
> > > From: Colin Ian King <colin.king@canonical.com>
> > >
> > > The while-loop iterates until src is non-null or i is 3, however, the
> > > loop counter i is not intinitialied to zero, causing incorrect iteration
> > > counts. Fix this by initializing it to zero.
> > >
> > > Addresses-Coverity: ("Uninitialized scalar variable")
> > > Fixes: 1aa5f2e2feed ("erofs: support decompress big pcluster for lz4 backend")
> > > Signed-off-by: Colin Ian King <colin.king@canonical.com>
> >
> > Thank you very much for catching this! It looks good to me,
> > Reviewed-by: Gao Xiang <hsiangkao@redhat.com>
> >
> > (btw, may I fold this into the original patchset? since such big pcluster
> > patchset is just applied to for-next for further integration testing, and
> > the commit id is not stable yet..)
> >
> > Thanks,
> > Gao Xiang
>
> I think this code is odd and would be more intelligible using
> a for loop like:
Thanks for your reply/suggestion.
> ---
> fs/erofs/decompressor.c | 20 ++++++++------------
> 1 file changed, 8 insertions(+), 12 deletions(-)
>
> diff --git a/fs/erofs/decompressor.c b/fs/erofs/decompressor.c
> index 27aa6a99b371..5a64f4649414 100644
> --- a/fs/erofs/decompressor.c
> +++ b/fs/erofs/decompressor.c
> @@ -286,28 +286,24 @@ static int z_erofs_decompress_generic(struct z_erofs_decompress_req *rq,
> }
>
> ret = alg->prepare_destpages(rq, pagepool);
> - if (ret < 0) {
> + if (ret < 0)
> return ret;
> - } else if (ret) {
> + if (ret) {
> dst = page_address(*rq->out);
> dst_maptype = 1;
> goto dstmap_out;
> }
I agree with the modification here, thanks!
>
> - i = 0;
> - while (1) {
> + for (i = 0; i < 3; i++) {
> dst = vm_map_ram(rq->out, nrpages_out, -1);
> -
> + if (dst) {
> + dst_maptype = 2;
> + goto dstmap_out;
> + }
> /* retry two more times (totally 3 times) */
> - if (dst || ++i >= 3)
> - break;
> vm_unmap_aliases();
That is not quite equivalent, since after trying more than 3 times,
(I think) no need to do the final vm_unmap_aliases(), since it's
only used for the next vm_map_ram(). Similar logic also see:
fs/xfs/xfs_buf.c: _xfs_buf_map_pages():
/*
* vm_map_ram() will allocate auxiliary structures (e.g.
* pagetables) with GFP_KERNEL, yet we are likely to be under
* GFP_NOFS context here. Hence we need to tell memory reclaim
* that we are in such a context via PF_MEMALLOC_NOFS to prevent
* memory reclaim re-entering the filesystem here and
* potentially deadlocking.
*/
nofs_flag = memalloc_nofs_save();
do {
bp->b_addr = vm_map_ram(bp->b_pages, bp->b_page_count,
-1);
if (bp->b_addr)
break;
vm_unmap_aliases();
} while (retried++ <= 1);
memalloc_nofs_restore(nofs_flag);
if (!bp->b_addr)
return -ENOMEM;
but yeah with some modification (and extra vm_unmap_aliases() here
as well...)
Thanks,
Gao Xiang
prev parent reply other threads:[~2021-04-07 3:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-06 16:27 Colin King
2021-04-06 23:54 ` Gao Xiang
2021-04-07 3:38 ` Joe Perches
2021-04-07 3:51 ` Gao Xiang [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=20210407035107.GA239118@xiangao.remote.csb \
--to=hsiangkao@redhat.com \
--cc=chao@kernel.org \
--cc=colin.king@canonical.com \
--cc=joe@perches.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-erofs@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=xiang@kernel.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
all inboxes | Powered by JetHome®