From: Michel Lespinasse <walken@google.com>
To: Sean Hefty <sean.hefty@intel.com>, LKML <linux-kernel@vger.kernel.org>
Subject: infiniband build warning
Date: Sun, 21 Jul 2013 18:37:58 -0700 [thread overview]
Message-ID: <20130722013758.GA14337@google.com> (raw)
Hi,
I am seeing build warnings in drivers/infiniband/core/cma.c starting with v3.11-rc1. These can be reproduced with gcc 4.6.3.
Would you consider applying the following fix ?
(The compiler warning seems benign as I could easily convince myself that the variable won't be used uninitialized, but I'd like to get rid of the compiler warning anyway).
--------------------------------- 8< ------------------------------------
infiniband: fix maybe-uninitialized warning in rdma_resolve_addr()
This fixes the following warning:
drivers/infiniband/core/cma.c: In function 'rdma_resolve_addr':
drivers/infiniband/core/cma.c:465:23: error: 'port' may be used uninitialized in this function [-Werror=maybe-uninitialized]
drivers/infiniband/core/cma.c:426:5: note: 'port' was declared here
The warning looks benign: port is only used after checking that
cma_dev is not NULL, and all assignments to cma_dev also set port.
diff --git a/drivers/infiniband/core/cma.c b/drivers/infiniband/core/cma.c
index f1c279fabe64..7b2e38ad1243 100644
--- a/drivers/infiniband/core/cma.c
+++ b/drivers/infiniband/core/cma.c
@@ -423,7 +423,7 @@ static int cma_resolve_ib_dev(struct rdma_id_private *id_priv)
struct sockaddr_ib *addr;
union ib_gid gid, sgid, *dgid;
u16 pkey, index;
- u8 port, p;
+ u8 port = 0, p;
int i;
cma_dev = NULL;
--
Michel "Walken" Lespinasse
A program is never fully debugged until the last user dies.
next reply other threads:[~2013-07-22 1:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-22 1:37 Michel Lespinasse [this message]
[not found] ` <20130722013758.GA14337-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
2013-07-22 5:40 ` infiniband build warning Hefty, Sean
2013-07-22 5:40 ` Hefty, Sean
2013-07-23 18:40 ` Or Gerlitz
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=20130722013758.GA14337@google.com \
--to=walken@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sean.hefty@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.