From: Mike Snitzer <snitzer@redhat.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Alasdair G Kergon <agk@redhat.com>,
Linux-Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: build warning after merge of the device-mapper tree
Date: Mon, 11 Dec 2017 00:24:36 -0500 [thread overview]
Message-ID: <20171211052436.GA18104@redhat.com> (raw)
In-Reply-To: <20171211130534.6ab6e415@canb.auug.org.au>
On Sun, Dec 10 2017 at 9:05pm -0500,
Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> Hi all,
>
> After merging the device-mapper tree, today's linux-next build (powerp
> ppc64_defconfig) produced this warning:
>
> drivers/md/dm.c: In function '__send_changing_extent_only':
> drivers/md/dm.c:1365:45: warning: 'ti' may be used uninitialized in this function [-Wmaybe-uninitialized]
> num_bios = get_num_bios ? get_num_bios(ti) : 0;
> ^
>
> Introduced by commit
>
> aecefd4919de ("dm: fix __send_changing_extent_only() to send first bio and chain remainder")
>
> This looks particularly bad :-(
I worked all weekend on DM code and compiled dm.c probably 30 times,
pretty bizarre that the RHEL7 gcc compiler isn't spewing anything about
this.
Anyway, I just fixed it via rebase (new commit is
6fb0326f0a19dd855bfd748481fd32035770376e).
Thanks,
Mike
next prev parent reply other threads:[~2017-12-11 5:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-11 2:05 linux-next: build warning after merge of the device-mapper tree Stephen Rothwell
2017-12-11 5:24 ` Mike Snitzer [this message]
2017-12-11 5:43 ` Stephen Rothwell
2018-09-18 1:53 Stephen Rothwell
2019-02-20 2:15 Stephen Rothwell
2019-02-20 3:35 ` Mike Snitzer
2020-07-09 3:26 Stephen Rothwell
2020-07-09 4:38 ` yangerkun
2021-01-22 6:56 Stephen Rothwell
2021-07-21 7:34 Stephen Rothwell
2021-08-10 9:31 ` Stephen Rothwell
2024-02-08 3:42 Stephen Rothwell
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=20171211052436.GA18104@redhat.com \
--to=snitzer@redhat.com \
--cc=agk@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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;
as well as URLs for NNTP newsgroup(s).