linux-kernel - Re: linux-next: build warning after merge of the gfs2 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-prev] [day] [month] [year] [list]

Message-ID: <CAHpGcMKKwtxcaHRuhVWzRNLK=Cpw1sBd9zOKP-zTbgOstM7tzg@mail.gmail.com>
Date:   Wed, 11 Dec 2019 00:20:49 +0100
From:   Andreas Grünbacher <andreas.gruenbacher@...il.com>
To:     Stephen Rothwell <sfr@...b.auug.org.au>
Cc:     Steven Whitehouse <swhiteho@...hat.com>,
        Bob Peterson <rpeterso@...hat.com>,
        Linux Next Mailing List <linux-next@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Andreas Gruenbacher <agruenba@...hat.com>
Subject: Re: linux-next: build warning after merge of the gfs2 tree

Hi Stephen,

Am Mi., 11. Dez. 2019 um 00:10 Uhr schrieb Stephen Rothwell
<sfr@...b.auug.org.au>:
> Hi all,
>
> After merging the gfs2 tree, today's linux-next build (x86_64
> allmodconfig) produced this warning:
>
> fs/gfs2/lops.c: In function 'gfs2_find_jhead':
> fs/gfs2/lops.c:536:13: warning: 'bio_chained' may be used uninitialized in this function [-Wmaybe-uninitialized]
>   536 |    if (!bio || (bio_chained && !off)) {
>       |        ~~~~~^~~~~~~~~~~~~~~~~~~~~~~~
>
> Introduced by commit
>
>   1ee366c67176 ("gfs2: Another gfs2_find_jhead fix")

thanks. It's actually a false positive and I'm not getting this
warning, but I'll make the code more explicit.

Andreas