From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752760AbcLFWiX (ORCPT ); Tue, 6 Dec 2016 17:38:23 -0500 Received: from ozlabs.org ([103.22.144.67]:56399 "EHLO ozlabs.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751905AbcLFWiV (ORCPT ); Tue, 6 Dec 2016 17:38:21 -0500 Date: Wed, 7 Dec 2016 09:38:19 +1100 From: Stephen Rothwell To: David Sterba Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org, Wang Xiaoguang Subject: Re: linux-next: build warning after merge of the btrfs-kdave tree Message-ID: <20161207093819.1d4358b1@canb.auug.org.au> In-Reply-To: <20161128110230.2e2bda87@canb.auug.org.au> References: <20161128110230.2e2bda87@canb.auug.org.au> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi David, On Mon, 28 Nov 2016 11:02:30 +1100 Stephen Rothwell wrote: > > After merging the btrfs-kdave tree, today's linux-next build (powerpc > ppc64_defconfig) produced this warning: > > fs/btrfs/inode.c: In function 'run_delalloc_range': > fs/btrfs/inode.c:1219:9: warning: 'cur_end' may be used uninitialized in this function [-Wmaybe-uninitialized] > start = cur_end + 1; > ^ > fs/btrfs/inode.c:1172:6: note: 'cur_end' was declared here > u64 cur_end; > ^ > > Introduced by commit > > cow_file_range_async ("btrfs: Introduce COMPRESS reserve type to fix false enospc for compression") > > Presumably a false positive because ASSERT(0) panics? Actually it does not if CONFIG_BTRFS_ASSERT is not set (which it isn't for the above build), so this is not a false positive. I am still seeing this. -- Cheers, Stephen Rothwell