From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephen Rothwell Subject: linux-next: build warning after merge of the tip tree Date: Wed, 14 Dec 2016 13:28:28 +1100 Message-ID: <20161214132828.1d128963@canb.auug.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Return-path: Received: from ozlabs.org ([103.22.144.67]:53957 "EHLO ozlabs.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753296AbcLNC2c (ORCPT ); Tue, 13 Dec 2016 21:28:32 -0500 Sender: linux-next-owner@vger.kernel.org List-ID: To: Thomas Gleixner , Ingo Molnar , "H. Peter Anvin" , Peter Zijlstra , Artem Bityutskiy Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org, Richard Weinberger Archived-At: List-Archive: List-Post: 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. -- Cheers, Stephen Rothwell