Re: [net-next PATCH] ipv6: fix false-postive maybe-uninitialized warning

2017-08-18 Thread Arnd Bergmann
On Fri, Aug 18, 2017 at 7:49 PM, David Miller wrote: > From: Arnd Bergmann > Date: Fri, 18 Aug 2017 13:34:22 +0200 >> >> This kind of warning involving an unlock between variable initialization >> and use is relatively frequent for false-positives. I should try to >> seek clarification from the

Re: [net-next PATCH] ipv6: fix false-postive maybe-uninitialized warning

2017-08-18 Thread David Miller
From: Arnd Bergmann Date: Fri, 18 Aug 2017 13:34:22 +0200 > Adding a lock around one of the assignments prevents gcc from > tracking the state of the local 'fibmatch' variable, so it can no > longer prove that 'dst' is always initialized, leading to a bogus > warning: > > net/ipv6/route.c: In fu

[net-next PATCH] ipv6: fix false-postive maybe-uninitialized warning

2017-08-18 Thread Arnd Bergmann
Adding a lock around one of the assignments prevents gcc from tracking the state of the local 'fibmatch' variable, so it can no longer prove that 'dst' is always initialized, leading to a bogus warning: net/ipv6/route.c: In function 'inet6_rtm_getroute': net/ipv6/route.c:3659:2: error: 'dst' may b