From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1754058AbcK1ACl (ORCPT <rfc822;w@1wt.eu>);
        Sun, 27 Nov 2016 19:02:41 -0500
Received: from ozlabs.org ([103.22.144.67]:58043 "EHLO ozlabs.org"
        rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
        id S1752964AbcK1ACd (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
        Sun, 27 Nov 2016 19:02:33 -0500
Date: Mon, 28 Nov 2016 11:02:30 +1100
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: David Sterba <dsterba@suse.cz>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
        Wang Xiaoguang <wangxg.fnst@cn.fujitsu.com>
Subject: linux-next: build warning after merge of the btrfs-kdave tree
Message-ID: <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: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

Hi David,

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?

-- 
Cheers,
Stephen Rothwell