From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jens Axboe Subject: Re: linux-next: build warnings after merge of the block tree Date: Tue, 26 Nov 2013 12:02:08 -0700 Message-ID: <5294F030.5090805@kernel.dk> References: <20131126132946.e402679788ae8269f0c5128a@canb.auug.org.au> <20131126143550.7a2195476ff4aa5c73db20b2@canb.auug.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: Received: from merlin.infradead.org ([205.233.59.134]:56130 "EHLO merlin.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752940Ab3KZTCx (ORCPT ); Tue, 26 Nov 2013 14:02:53 -0500 In-Reply-To: Sender: linux-next-owner@vger.kernel.org List-ID: To: Olof Johansson , Stephen Rothwell Cc: "linux-next@vger.kernel.org" , "linux-kernel@vger.kernel.org" , Kent Overstreet On 11/26/2013 12:01 PM, Olof Johansson wrote: > On Mon, Nov 25, 2013 at 7:35 PM, Stephen Rothwell wrote: >> Hi all, >> >> On Tue, 26 Nov 2013 13:29:46 +1100 Stephen Rothwell wrote: >>> >>> After merging the block tree, today's linux-next build (arm >>> multi_v7_defconfig) produced these warnings: >>> >>> block/blk-merge.c: In function 'blk_rq_map_sg': >>> block/blk-merge.c:133:8: warning: 'bvprv.bv_len' may be used uninitialized in this function [-Wuninitialized] >>> block/blk-merge.c:171:23: note: 'bvprv.bv_len' was declared here >>> block/blk-merge.c:133:8: warning: 'bvprv.bv_page' may be used uninitialized in this function [-Wuninitialized] >>> block/blk-merge.c:171:23: note: 'bvprv.bv_page' was declared here >>> block/blk-merge.c:133:8: warning: 'bvprv.bv_offset' may be used uninitialized in this function [-Wuninitialized] >>> block/blk-merge.c:171:23: note: 'bvprv.bv_offset' was declared here >>> block/blk-merge.c: In function 'blk_bio_map_sg': >>> block/blk-merge.c:133:8: warning: 'bvprv.bv_len' may be used uninitialized in this function [-Wuninitialized] >>> block/blk-merge.c:233:23: note: 'bvprv.bv_len' was declared here >>> block/blk-merge.c:133:8: warning: 'bvprv.bv_offset' may be used uninitialized in this function [-Wuninitialized] >>> block/blk-merge.c:233:23: note: 'bvprv.bv_offset' was declared here >>> block/blk-merge.c:133:8: warning: 'bvprv.bv_page' may be used uninitialized in this function [-Wuninitialized] >>> block/blk-merge.c:233:23: note: 'bvprv.bv_page' was declared here >>> block/blk-merge.c: In function 'attempt_merge': >>> block/blk-merge.c:108:7: warning: 'end_bv.bv_offset' may be used uninitialized in this function [-Wuninitialized] >>> block/blk-merge.c:89:17: note: 'end_bv.bv_offset' was declared here >>> block/blk-merge.c:108:7: warning: 'end_bv.bv_page' may be used uninitialized in this function [-Wuninitialized] >>> block/blk-merge.c:89:17: note: 'end_bv.bv_page' was declared here >>> block/blk-merge.c:108:7: warning: 'end_bv.bv_len' may be used uninitialized in this function [-Wuninitialized] >>> block/blk-merge.c:89:17: note: 'end_bv.bv_len' was declared here >>> >>> arm has its own definition of BIOVEC_PHYS_MERGEABLE() if that is relevant. >> >> For an easier test case, the i386 defcongig does this as well. > > I just noticed that i see this with gcc 4.7.0, but 4.8.1 does not warn. That's good, because it's not a bug. But arguably we should shut up 4.7 as well, however... -- Jens Axboe