From: Anand Jain <anand.jain@oracle.com>
To: Qu Wenruo <quwenruo.btrfs@gmx.com>,
zhangshida <starzhangzsd@gmail.com>,
clm@fb.com, josef@toxicpanda.com, dsterba@suse.com
Cc: linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org,
zhangshida@kylinos.cn, k2ci <kernel-bot@kylinos.cn>
Subject: Re: [PATCH] btrfs: fix uninitialized warning in btrfs_log_inode
Date: Wed, 17 May 2023 17:13:17 +0800 [thread overview]
Message-ID: <28116d72-d3a6-540d-fea8-542dd5d5ca54@oracle.com> (raw)
In-Reply-To: <f90eb6c1-4491-ecd2-1fdd-56580088c993@gmx.com>
On 17/5/23 15:46, Qu Wenruo wrote:
>
>
> On 2023/5/16 09:34, zhangshida wrote:
>> From: Shida Zhang <zhangshida@kylinos.cn>
>>
>> From: Shida Zhang <zhangshida@kylinos.cn>
>>
>> This fixes the following warning reported by gcc 10 under x86_64:
>
> Full gcc version please.
> Especially you need to check if your gcc10 is the latest release.
>
> If newer gcc (12.2.1) tested without such error, it may very possible to
> be a false alert.
>
> And in fact it is.
>
I also noticed that last_range_start is not actually uninitialized.
However, it is acceptable to initialize a variable to silence the
compiler if necessary, right? We have done something similar in the
past.
Thanks, Anand
> @first_dir_index would only be assigned to @last_range_start if
> last_range_end != 0.
>
> Thus the loop must have to be executed once, and @last_range_start won't
> be zero.
>
> Please do check your environment (especially your gcc version and
> backports), before sending such trivial patches.
> Under most cases, it helps nobody.
>
> Thanks,
> Qu
>
>>
>> ../fs/btrfs/tree-log.c: In function ‘btrfs_log_inode’:
>> ../fs/btrfs/tree-log.c:6211:9: error: ‘last_range_start’ may be used
>> uninitialized in this function [-Werror=maybe-uninitialized]
>> 6211 | ret = insert_dir_log_key(trans, log, path, key.objectid,
>> | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>> 6212 | first_dir_index, last_dir_index);
>> | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>> ../fs/btrfs/tree-log.c:6161:6: note: ‘last_range_start’ was declared here
>> 6161 | u64 last_range_start;
>> | ^~~~~~~~~~~~~~~~
>>
>> Reported-by: k2ci <kernel-bot@kylinos.cn>
>> Signed-off-by: Shida Zhang <zhangshida@kylinos.cn>
>> ---
>> fs/btrfs/tree-log.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/fs/btrfs/tree-log.c b/fs/btrfs/tree-log.c
>> index 9b212e8c70cc..d2755d5e338b 100644
>> --- a/fs/btrfs/tree-log.c
>> +++ b/fs/btrfs/tree-log.c
>> @@ -6158,7 +6158,7 @@ static int
>> log_delayed_deletions_incremental(struct btrfs_trans_handle *trans,
>> {
>> struct btrfs_root *log = inode->root->log_root;
>> const struct btrfs_delayed_item *curr;
>> - u64 last_range_start;
>> + u64 last_range_start = 0;
>> u64 last_range_end = 0;
>> struct btrfs_key key;
>>
next prev parent reply other threads:[~2023-05-17 9:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-16 1:34 zhangshida
2023-05-17 3:23 ` Anand Jain
2023-05-17 7:46 ` Qu Wenruo
2023-05-17 9:07 ` Stephen Zhang
2023-05-17 9:49 ` Qu Wenruo
2023-05-22 21:51 ` David Sterba
2023-05-23 10:47 ` Qu Wenruo
2023-05-24 9:23 ` David Sterba
2023-05-17 9:13 ` Anand Jain [this message]
2023-05-17 9:39 ` Qu Wenruo
2023-05-22 21:35 ` David Sterba
2023-05-22 21:52 ` David Sterba
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=28116d72-d3a6-540d-fea8-542dd5d5ca54@oracle.com \
--to=anand.jain@oracle.com \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=josef@toxicpanda.com \
--cc=kernel-bot@kylinos.cn \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quwenruo.btrfs@gmx.com \
--cc=starzhangzsd@gmail.com \
--cc=zhangshida@kylinos.cn \
/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®