Re: linux-next: build warning after merge of the tip tree
From: Richard Weinberger <richard@nod.at>
Date: 2016-12-14 08:13:01
Also in:
lkml
From: Richard Weinberger <richard@nod.at>
Date: 2016-12-14 08:13:01
Also in:
lkml
Stephen, Ingo, CC'ing David. On 14.12.2016 08:24, Ingo Molnar wrote:
* Stephen Rothwell [off-list ref] wrote:quoted
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