linux-kernel - linux-next: build warnings 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: Windows password security audit tool. GUI, reports in PDF.

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

Date:   Wed, 15 Jan 2020 09:30:04 +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>,
        Nikolay Borisov <nborisov@...e.com>
Subject: linux-next: build warnings after merge of the btrfs tree

Hi all,

After merging the btrfs tree, today's linux-next build (powerpc
ppc64_defconfig) produced these warnings:

fs/btrfs/block-group.c: In function 'exclude_super_stripes':
fs/btrfs/block-group.c:1706:5: warning: 'logical' may be used uninitialized in this function [-Wmaybe-uninitialized]
 1706 |     kfree(logical);
      |     ^~~~~~~~~~~~~~
fs/btrfs/block-group.c:1691:20: warning: 'stripe_len' may be used uninitialized in this function [-Wmaybe-uninitialized]
 1691 |    if (logical[nr] + stripe_len <= cache->start)
      |        ~~~~~~~~~~~~^~~~~~~~~~~~

Introduced by commit

  767f58cdaf20 ("btrfs: Refactor btrfs_rmap_block to improve readability")

btrfs_rmap_block() returns zero even if its output arguments are not
assigned to ... maybe the final "return 0" should be "return ret"?

-- 
Cheers,
Stephen Rothwell

Content of type "application/pgp-signature" skipped