From: Jens Axboe <axboe@fb.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] SG changes for 4.3
Date: Wed, 2 Sep 2015 16:50:51 -0600 [thread overview]
Message-ID: <55E77D4B.2020604@fb.com> (raw)
In-Reply-To: <55E77B00.4040302@fb.com>
On 09/02/2015 04:41 PM, Jens Axboe wrote:
> On 09/02/2015 04:34 PM, Linus Torvalds wrote:
>> Jens,
>>
>> On Wed, Sep 2, 2015 at 9:58 AM, Jens Axboe <axboe@fb.com> wrote:
>>>
>>> This pull request contains a set of scatter-gather related changes/fixes
>>> for 4.3. It contains:
>>
>> This results in several new and annoying warnings. They may all be ok
>> code, but they are very distracting. Please stop introducing new
>> warnings to the build, because by now most of the warnings I see come
>> from the block layer.
>>
>> block/blk-merge.c: In function ‘blk_queue_split’:
>> include/linux/blkdev.h:1368:21: warning: ‘bvprv.bv_offset’ may be
>> used uninitialized in this function [-Wmaybe-uninitialized]
>> ((bprv->bv_offset + bprv->bv_len) & queue_virt_boundary(q));
>>
>> (it gives this for bv_len too). The reason seems to be that disgusting
>> situation where "bvprv" is uninitiatlized unless "split" is true, and
>> the code looks like it is correct, but the compiler clearly has a hard
>> time seeing it. It took me a while too, so I can't really blame it.
>>
>> Either initialize bvprv to something explicit, or make the code clear
>> enough that the compiler can see that it is never used uninitialized.
>> Because those compiler warnings are sometimes real, and we can't just
>> ignore them.
>>
>> There was another type-based warning introduced by your core block
>> pull (size_t vs unsigned int).
>
> I think it's a repeat offender that got reintroduced. I'll fix it up.
This seems to make it happier. Will go out later in the merge window.
http://git.kernel.dk/cgit/linux-block/commit/?h=for-linus&id=5014c311baa2b21384321fa4a9f617a92e3e56f0
--
Jens Axboe
next prev parent reply other threads:[~2015-09-02 22:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-02 16:58 [GIT PULL] SG changes for 4.3 Jens Axboe
2015-09-02 22:34 ` Linus Torvalds
2015-09-02 22:41 ` Jens Axboe
2015-09-02 22:50 ` Jens Axboe [this message]
2015-09-03 4:28 ` Ming Lin
2015-09-03 14:31 ` Jens Axboe
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=55E77D4B.2020604@fb.com \
--to=axboe@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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