From: Stephen Rothwell <sfr@canb.auug.org.au>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: "Martin K. Petersen" <martin.petersen@oracle.com>,
Linux-Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Hannes Reinecke <hare@suse.de>,
Johannes Thumshirn <jth@kernel.org>
Subject: Re: linux-next: build warning after merge of the scsi-mkp tree
Date: Thu, 12 Jul 2018 14:30:57 +1000 [thread overview]
Message-ID: <20180712143057.49bfcab5@canb.auug.org.au> (raw)
In-Reply-To: <20180711141737.57c1e26f@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 1164 bytes --]
Hi all,
On Wed, 11 Jul 2018 14:17:37 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> After merging the scsi-mkp tree, today's linux-next build (x86_64
> allmodconfig) produced this warning:
>
> In file included from include/linux/spinlock_types.h:18:0,
> from include/linux/spinlock.h:82,
> from drivers/scsi/libfc/fc_rport.c:61:
> drivers/scsi/libfc/fc_rport.c: In function 'fc_rport_recv_req':
> include/linux/lockdep.h:347:45: warning: 'rdata' may be used uninitialized in this function [-Wmaybe-uninitialized]
> #define lockdep_is_held(lock) lock_is_held(&(lock)->dep_map)
> ^
> drivers/scsi/libfc/fc_rport.c:1832:24: note: 'rdata' was declared here
> struct fc_rport_priv *rdata;
> ^~~~~
>
> Introduced by commit
>
> ee35624e1e4e ("scsi: libfc: Add lockdep annotations")
>
> It is actually complaining about function fc_rport_recv_plogi_req()
> (presumably it is being inlined) and this looks like an actual bug :-(
This warning now appears after the merge of the scsi tree.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2018-07-12 4:30 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-11 4:17 linux-next: build warning after merge of the scsi-mkp tree Stephen Rothwell
2018-07-12 4:30 ` Stephen Rothwell [this message]
2018-07-12 6:10 ` Hannes Reinecke
-- strict thread matches above, loose matches on Subject: below --
2023-08-28 3:13 Stephen Rothwell
2023-07-24 4:04 Stephen Rothwell
2023-07-26 2:13 ` Martin K. Petersen
2023-05-23 3:38 Stephen Rothwell
2023-05-23 6:38 ` Damien Le Moal
2023-05-23 7:49 ` Damien Le Moal
2021-10-18 20:41 Stephen Rothwell
2021-11-08 0:06 ` Stephen Rothwell
2021-11-08 14:36 ` James Bottomley
2020-03-02 2:35 Stephen Rothwell
2020-03-02 14:36 ` Brian King
2020-03-06 4:52 ` Stephen Rothwell
2020-03-06 15:30 ` Brian King
2018-12-20 6:34 Stephen Rothwell
2018-10-12 5:10 Stephen Rothwell
2017-09-26 4:09 Stephen Rothwell
2017-09-27 3:27 ` Stephen Rothwell
2017-08-24 5:57 Stephen Rothwell
2017-08-24 5:59 ` Stephen Rothwell
2016-11-14 5:16 Stephen Rothwell
2016-11-14 12:31 ` Christoph Hellwig
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=20180712143057.49bfcab5@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=James.Bottomley@HansenPartnership.com \
--cc=hare@suse.de \
--cc=jth@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=martin.petersen@oracle.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).