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: Re: linux-next: build warning after merge of the btrfs-kdave tree
Date: Wed, 7 Dec 2016 09:38:19 +1100 [thread overview]
Message-ID: <20161207093819.1d4358b1@canb.auug.org.au> (raw)
In-Reply-To: <20161128110230.2e2bda87@canb.auug.org.au>
Hi David,
On Mon, 28 Nov 2016 11:02:30 +1100 Stephen Rothwell <sfr@canb•auug.org.au> 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
next prev parent reply other threads:[~2016-12-06 22:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-28 0:02 linux-next: build warning after merge of the btrfs-kdave tree Stephen Rothwell
2016-12-06 22:38 ` Stephen Rothwell [this message]
2016-12-14 15:19 ` David Sterba
-- strict thread matches above, loose matches on Subject: below --
2017-05-17 23:41 Stephen Rothwell
2017-05-18 12:50 ` David Sterba
2017-05-25 1:31 ` Stephen Rothwell
2017-12-19 22:20 Stephen Rothwell
2017-12-20 0:12 ` Qu Wenruo
2017-12-21 16:49 ` David Sterba
2017-12-22 0:32 ` Qu Wenruo
2018-11-26 0:06 Stephen Rothwell
2018-11-26 7:56 ` Christoph Hellwig
2019-01-23 22:53 Stephen Rothwell
2019-01-28 16:53 ` David Sterba
2019-05-03 0:21 Stephen Rothwell
2019-05-03 13:37 ` David Sterba
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20161207093819.1d4358b1@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=dsterba@suse$(echo .)cz \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=wangxg.fnst@cn$(echo .)fujitsu.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox