linux-kernel - Re: Boot failure on Arndale with next-20131105

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <20131108194511.545e99151b4fe5efb9ed6f0f@canb.auug.org.au>
Date:	Fri, 8 Nov 2013 19:45:11 +1100
From:	Stephen Rothwell <sfr@...b.auug.org.au>
To:	Jens Axboe <axboe@...nel.dk>
Cc:	Stephen Warren <swarren@...dotorg.org>,
	Tomasz Figa <t.figa@...sung.com>,
	Tushar Behera <tushar.behera@...aro.org>,
	linux-next@...r.kernel.org, lkml <linux-kernel@...r.kernel.org>,
	Chris Mason <chris.mason@...ionio.com>
Subject: Re: Boot failure on Arndale with next-20131105

Hi Jens,

On Tue, 05 Nov 2013 14:25:00 -0700 Jens Axboe <axboe@...nel.dk> wrote:
>
> On 11/05/2013 10:38 AM, Stephen Warren wrote:
> > I note that compiling next-20131105 generates quite a few warnings re:
> > uninitialized variables. Reverting the commit doesn't solve those.
> > 
> >> 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 [-Wmaybe-uninitialized]
> >> 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 [-Wmaybe-uninitialized]
> >> 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 [-Wmaybe-uninitialized]
> >> block/blk-merge.c:233:23: note: ‘bvprv.bv_page’ was declared here
> >> block/blk-merge.c: In function ‘blk_rq_map_sg’:
> >> block/blk-merge.c:133:8: warning: ‘bvprv.bv_page’ may be used uninitialized in this function [-Wmaybe-uninitialized]
> >> 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 [-Wmaybe-uninitialized]
> >> block/blk-merge.c:171:23: note: ‘bvprv.bv_offset’ was declared here
> >> block/blk-merge.c:133:8: warning: ‘bvprv.bv_len’ may be used uninitialized in this function [-Wmaybe-uninitialized]
> >> block/blk-merge.c:171:23: note: ‘bvprv.bv_len’ 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 [-Wmaybe-uninitialized]
> >> 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 [-Wmaybe-uninitialized]
> >> 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 [-Wmaybe-uninitialized]
> >> block/blk-merge.c:89:17: note: ‘end_bv.bv_len’ was declared here
> 
> Looks like an incomplete merge. The patch to silence those warnings
> (which aren't bugs, BTW) is definitely in my for-next branch.

I am still getting those warnings in linux-next for various builds
(include 1386 defconfig).  Any hints would be good.

-- 
Cheers,
Stephen Rothwell                    sfr@...b.auug.org.au

Content of type "application/pgp-signature" skipped