From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Alasdair G Kergon <agk@redhat.com>, Mike Snitzer <snitzer@redhat.com>
Cc: Linux-Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: linux-next: build warning after merge of the device-mapper tree
Date: Mon, 11 Dec 2017 13:05:34 +1100 [thread overview]
Message-ID: <20171211130534.6ab6e415@canb.auug.org.au> (raw)
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 :-(
--
Cheers,
Stephen Rothwell
next reply other threads:[~2017-12-11 2:05 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-11 2:05 Stephen Rothwell [this message]
2017-12-11 5:24 ` linux-next: build warning after merge of the device-mapper tree Mike Snitzer
2017-12-11 5:43 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
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
2024-07-09 8:57 Stephen Rothwell
2024-07-09 9:56 ` Mikulas Patocka
2024-07-09 22:28 ` Stephen Rothwell
2024-07-10 15:48 ` Mikulas Patocka
2024-07-30 10:07 ` Stephen Rothwell
2024-07-30 11:54 ` Mikulas Patocka
2024-07-30 13:36 ` 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=20171211130534.6ab6e415@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=agk@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=snitzer@redhat.com \
/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).