From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mout.kundenserver.de ([212.227.17.10]:61193 "EHLO mout.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932768AbcIXU5j (ORCPT ); Sat, 24 Sep 2016 16:57:39 -0400 From: Arnd Bergmann To: linaro-kernel@lists.linaro.org Cc: Build bot for Mark Brown , kernel-build-reports@lists.linaro.org, stable@vger.kernel.org, gregkh@linuxfoundation.org, Trond Myklebust Subject: Re: v4.7.5 build: 0 failures 2 warnings (v4.7.5) Date: Sat, 24 Sep 2016 22:57:27 +0200 Message-ID: <2364242.iAJVmYQbD8@wuerfel> In-Reply-To: References: MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Sender: stable-owner@vger.kernel.org List-ID: On Saturday, September 24, 2016 2:44:46 PM CEST Build bot for Mark Brown wrote: > > Warnings Summary: 2 > 5 ../fs/nfs/nfs4session.c:201:54: warning: 'cur_seq' may be used uninitialized in this function [-Wmaybe-uninitialized] This is a false positive warning that was introduced by Fixes: 11d01071d730 ("NFSv4.1: Fix Oopsable condition in server callback races") I submitted a patch at https://patchwork.kernel.org/patch/9307119/ which still seems like the best workaround to me, but as the warning is disabled in v4.8, the patch was never applied upstream. > 1 ../fs/reiserfs/ibalance.c:1156:2: warning: 'new_insert_key' may be used uninitialized in this function [-Wmaybe-uninitialized] This one was the last warning reported by Mark's autobuilder in v4.7, the following patch for it went into v4.8: Fixes: 0a11b9aae49a ("reiserfs: fix "new_insert_key may be used uninitialized ..."") Arnd