From: Matthew Wilcox <willy@infradead.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Rong Tao <rtoax@foxmail.com>, Rong Tao <rongtao@cestc.cn>,
wuchi <wuchi.zero@gmail.com>,
open list <linux-kernel@vger.kernel.org>,
linux-mm@kvack.org
Subject: Re: [PATCH] radix tree test suite: Fix uninitialized variable compilation warning
Date: Thu, 10 Nov 2022 16:06:13 +0000 [thread overview]
Message-ID: <Y20hded53owR/dPo@casper.infradead.org> (raw)
In-Reply-To: <20221109162348.3dbde3a7942c303af012276c@linux-foundation.org>
On Wed, Nov 09, 2022 at 04:23:48PM -0800, Andrew Morton wrote:
> On Wed, 9 Nov 2022 22:34:25 +0800 Rong Tao <rtoax@foxmail.com> wrote:
>
> > [PATCH] radix tree test suite: Fix uninitialized variable compilation warning
>
> This is not the test suite.
>
> > We need to set an initial value for offset to eliminate compilation
> > warning.
> >
> > How to reproduce warning:
> >
> > $ make -C tools/testing/radix-tree
> > radix-tree.c: In function ‘radix_tree_tag_clear’:
> > radix-tree.c:1046:17: warning: ‘offset’ may be used uninitialized in this function [-Wmaybe-uninitialized]
> > 1046 | node_tag_clear(root, parent, tag, offset);
> > | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> >
> > ...
> >
> > --- a/lib/radix-tree.c
> > +++ b/lib/radix-tree.c
> > @@ -1029,7 +1029,7 @@ void *radix_tree_tag_clear(struct radix_tree_root *root,
> > {
> > struct radix_tree_node *node, *parent;
> > unsigned long maxindex;
> > - int offset;
> > + int offset = 0;
> >
> > radix_tree_load_root(root, &node, &maxindex);
> > if (index > maxindex)
>
> Are we sure this isn't actually a bug? What happens if the tree is empty?
If the tree is empty, then node is NULL and we never use offset.
The compiler is too stupid to know this. This warning is only observed
when building the test suite and not when building the kernel itself.
I'm not sure the patch is worth it, tbh.
prev parent reply other threads:[~2022-11-10 16:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <tencent_DF74099967595DCEA93CBDC28D062026180A@qq.com>
2022-11-10 0:23 ` Andrew Morton
2022-11-10 5:00 ` [PATCH] lib/radix-tree: " Rong Tao
2022-11-10 16:06 ` Matthew Wilcox
2022-11-11 2:11 ` Rong Tao
2022-11-10 16:06 ` Matthew Wilcox [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=Y20hded53owR/dPo@casper.infradead.org \
--to=willy@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rongtao@cestc.cn \
--cc=rtoax@foxmail.com \
--cc=wuchi.zero@gmail.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