From: David Sterba <dsterba@suse.cz>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Johannes Thumshirn <johannes.thumshirn@wdc.com>
Subject: Re: linux-next: build warning after merge of the btrfs tree
Date: Mon, 24 Feb 2020 15:34:29 +0100 [thread overview]
Message-ID: <20200224143429.GR2902@suse.cz> (raw)
In-Reply-To: <20200224095735.179fe582@canb.auug.org.au>
On Mon, Feb 24, 2020 at 09:57:35AM +1100, Stephen Rothwell wrote:
> Hi all,
>
> After merging the btrfs tree, today's linux-next build (x86_64
> allmodconfig) produced this warning:
>
> fs/btrfs/check-integrity.c: In function 'btrfsic_process_superblock_dev_mirror':
> fs/btrfs/check-integrity.c:916:9: warning: 'ret' may be used uninitialized in this function [-Wmaybe-uninitialized]
> 916 | return ret;
> | ^~~
>
> Introduced by commit
>
> 5a03d907a555 ("btrfs: remove buffer_heads form super block mirror integrity checking")
>
> I think this is not a false positive since ret is only assigned is a
> "goto out" is executed.
Yes that sounds correct, will be fixed in next update, thanks.
next prev parent reply other threads:[~2020-02-24 14:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-23 22:57 linux-next: build warning after merge of the btrfs tree Stephen Rothwell
2020-02-24 14:34 ` David Sterba [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-07-22 1:03 Stephen Rothwell
2021-01-26 23:18 Stephen Rothwell
2021-01-27 19:46 ` David Sterba
2020-08-25 0:45 Stephen Rothwell
2020-02-11 22:10 Stephen Rothwell
2020-02-12 16:03 ` David Sterba
2020-02-20 22:32 ` Stephen Rothwell
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=20200224143429.GR2902@suse.cz \
--to=dsterba@suse.cz \
--cc=johannes.thumshirn@wdc.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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;
as well as URLs for NNTP newsgroup(s).