[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20161214072411.GA1635@gmail.com>
Date: Wed, 14 Dec 2016 08:24:11 +0100
From: Ingo Molnar <mingo@...nel.org>
To: Stephen Rothwell <sfr@...b.auug.org.au>
Cc: Thomas Gleixner <tglx@...utronix.de>, Ingo Molnar <mingo@...e.hu>,
"H. Peter Anvin" <hpa@...or.com>,
Peter Zijlstra <peterz@...radead.org>,
Artem Bityutskiy <dedekind1@...il.com>,
linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
Richard Weinberger <richard@....at>
Subject: Re: linux-next: build warning after merge of the tip tree
* Stephen Rothwell <sfr@...b.auug.org.au> 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.
Thanks,
Ingo
Powered by blists - more mailing lists