From: Greg KH <gregkh@linuxfoundation.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: linaro-kernel@lists.linaro.org,
Build bot for Mark Brown <broonie@kernel.org>,
kernel-build-reports@lists.linaro.org, stable@vger.kernel.org,
Trond Myklebust <trondmy@primarydata.com>
Subject: Re: v4.7.5 build: 0 failures 2 warnings (v4.7.5)
Date: Sun, 25 Sep 2016 15:27:18 +0200 [thread overview]
Message-ID: <20160925132718.GA8415@kroah.com> (raw)
In-Reply-To: <2364242.iAJVmYQbD8@wuerfel>
On Sat, Sep 24, 2016 at 10:57:27PM +0200, Arnd Bergmann wrote:
> 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.
Sad :(
>
> > 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 ..."")
Thanks, now queued this one up as well.
greg k-h
next prev parent reply other threads:[~2016-09-25 13:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-24 13:44 v4.7.5 build: 0 failures 2 warnings (v4.7.5) Build bot for Mark Brown
2016-09-24 20:57 ` Arnd Bergmann
2016-09-25 13:27 ` Greg KH [this message]
2016-09-25 15:03 ` Greg KH
2016-09-25 23:46 ` Arnd Bergmann
2016-09-26 9:01 ` Greg KH
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160925132718.GA8415@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=arnd@arndb.de \
--cc=broonie@kernel.org \
--cc=kernel-build-reports@lists.linaro.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=stable@vger.kernel.org \
--cc=trondmy@primarydata.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.