[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20161129121206.32xn7gmrtv42s6nm@alphalink.fr>
Date: Tue, 29 Nov 2016 13:12:07 +0100
From: Guillaume Nault <g.nault@...halink.fr>
To: kbuild test robot <lkp@...el.com>
Cc: kbuild-all@...org, netdev@...r.kernel.org,
James Chapman <jchapman@...alix.com>,
Chris Elston <celston@...alix.com>
Subject: Re: [PATCH net 3/5] l2tp: fix racy socket lookup in l2tp_ip and
l2tp_ip6 bind()
On Tue, Nov 29, 2016 at 05:10:40AM +0800, kbuild test robot wrote:
> Hi Guillaume,
>
> [auto build test WARNING on net/master]
>
> url: https://github.com/0day-ci/linux/commits/Guillaume-Nault/l2tp-fixes-for-l2tp_ip-and-l2tp_ip6-socket-handling/20161129-043208
> config: x86_64-rhel (attached as .config)
> compiler: gcc-6 (Debian 6.2.0-3) 6.2.0 20160901
> reproduce:
> # save the attached .config to linux build tree
> make ARCH=x86_64
>
> Note: it may well be a FALSE warning. FWIW you are at least aware of it now.
> http://gcc.gnu.org/wiki/Better_Uninitialized_Warnings
>
> All warnings (new ones prefixed by >>):
>
> net/l2tp/l2tp_ip.c: In function 'l2tp_ip_bind':
> >> net/l2tp/l2tp_ip.c:299:9: warning: 'ret' may be used uninitialized in this function [-Wmaybe-uninitialized]
> return ret;
> ^~~
>
I should have seen this earlier, sorry.
This is now fixed in v2.
Powered by blists - more mailing lists