From mboxrd@z Thu Jan 1 00:00:00 1970 From: Richard Weinberger Subject: Re: linux-next: build warning after merge of the tip tree Date: Wed, 14 Dec 2016 09:05:10 +0100 Message-ID: References: <20161214132828.1d128963@canb.auug.org.au> <20161214072411.GA1635@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 8bit Return-path: Received: from b.ns.miles-group.at ([95.130.255.144]:44724 "EHLO radon.swed.at" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1754923AbcLNIL7 (ORCPT ); Wed, 14 Dec 2016 03:11:59 -0500 In-Reply-To: <20161214072411.GA1635@gmail.com> Sender: linux-next-owner@vger.kernel.org List-ID: To: Ingo Molnar , Stephen Rothwell Cc: Thomas Gleixner , Ingo Molnar , "H. Peter Anvin" , Peter Zijlstra , Artem Bityutskiy , linux-next@vger.kernel.org, linux-kernel@vger.kernel.org, David Gstir Stephen, Ingo, CC'ing David. On 14.12.2016 08:24, Ingo Molnar wrote: > > * Stephen Rothwell wrote: > >> Hi all, >> >> After merging the tip tree, today's linux-next build (x86_64 allmodconfig) >> produced this warning: >> >> fs/ubifs/dir.c: In function 'ubifs_readdir': >> fs/ubifs/dir.c:629:13: warning: 'fstr_real_len' may be used uninitialized in this function [-Wmaybe-uninitialized] >> fstr.len = fstr_real_len; >> ^ >> >> Introduced by commit >> >> f4f61d2cc6d8 ("ubifs: Implement encrypted filenames") >> >> This is a false positive because assignment and use are both protected by >> "if (encrypted)". >> >> I have no idea why this did not turn up earlier in my builds. > > FYI, f4f61d2cc6d8 is not in the -tip tree, so it cannot possibly have introduced > this warning. The commit comes via my UBIFS tree. But I never saw this warning, I'm testing with both gcc-4.8 and gcc-6.1. Let me investigate into that. Does today's tip change some compiler flags? Thanks, //richard