linux-kernel - linux-next: build warning after merge of the btrfs tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <20200224095735.179fe582@canb.auug.org.au>
Date:   Mon, 24 Feb 2020 09:57:35 +1100
From:   Stephen Rothwell <sfr@...b.auug.org.au>
To:     David Sterba <dsterba@...e.cz>
Cc:     Linux Next Mailing List <linux-next@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Johannes Thumshirn <johannes.thumshirn@....com>
Subject: linux-next: build warning after merge of the btrfs tree

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.

-- 
Cheers,
Stephen Rothwell

Content of type "application/pgp-signature" skipped