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. -- Jens Axboe -- To unsubscribe from this list: send the line "unsubscribe linux-next" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
