[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20200420224210.dff005bc62957a4d81d58226@linux-foundation.org>
Date: Mon, 20 Apr 2020 22:42:10 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Matthew Wilcox <willy@...radead.org>
Cc: linux-fsdevel@...r.kernel.org, linux-mm@...ck.org,
linux-kernel@...r.kernel.org, linux-btrfs@...r.kernel.org,
linux-erofs@...ts.ozlabs.org, linux-ext4@...r.kernel.org,
linux-f2fs-devel@...ts.sourceforge.net, cluster-devel@...hat.com,
ocfs2-devel@....oracle.com, linux-xfs@...r.kernel.org,
Gao Xiang <gaoxiang25@...wei.com>,
Dave Chinner <dchinner@...hat.com>,
William Kucharski <william.kucharski@...cle.com>,
Chao Yu <yuchao0@...wei.com>
Subject: Re: [PATCH v11 19/25] erofs: Convert compressed files from
readpages to readahead
On Tue, 14 Apr 2020 08:02:27 -0700 Matthew Wilcox <willy@...radead.org> wrote:
>
> Use the new readahead operation in erofs.
>
Well this is exciting.
fs/erofs/data.c: In function erofs_raw_access_readahead:
fs/erofs/data.c:149:18: warning: last_block may be used uninitialized in this function [-Wmaybe-uninitialized]
*last_block + 1 != current_block) {
It seems to be a preexisting bug, which your patch prompted gcc-7.2.0
to notice.
erofs_read_raw_page() goes in and uses *last_block, but neither of its
callers has initialized it. Could the erofs maintainers please take a
look?
Powered by blists - more mailing lists