Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
MIME-Version: 1.0
References: <20191211101004.35db8a07@canb.auug.org.au>
In-Reply-To: <20191211101004.35db8a07@canb.auug.org.au>
From:   =?UTF-8?Q?Andreas_Gr=C3=BCnbacher?= <andreas.gruenbacher@gmail.com>
Date:   Wed, 11 Dec 2019 00:20:49 +0100
Message-ID: <CAHpGcMKKwtxcaHRuhVWzRNLK=Cpw1sBd9zOKP-zTbgOstM7tzg@mail.gmail.com>
Subject: Re: linux-next: build warning after merge of the gfs2 tree
To:     Stephen Rothwell <sfr@canb.auug.org.au>
Cc:     Steven Whitehouse <swhiteho@redhat.com>,
        Bob Peterson <rpeterso@redhat.com>,
        Linux Next Mailing List <linux-next@vger.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
        Andreas Gruenbacher <agruenba@redhat.com>
Content-Type: text/plain; charset="UTF-8"
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

Hi Stephen,

Am Mi., 11. Dez. 2019 um 00:10 Uhr schrieb Stephen Rothwell
<sfr@canb.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