From: Doug Ledford <dledford@redhat.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: linux-rdma@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] infiniband: shut up a maybe-uninitialized warning
Date: Tue, 02 Aug 2016 13:45:25 -0400 [thread overview]
Message-ID: <1470159925.18081.21.camel@redhat.com> (raw)
In-Reply-To: <20160704150659.2883024-1-arnd@arndb.de>
[-- Attachment #1: Type: text/plain, Size: 2005 bytes --]
On Mon, 2016-07-04 at 17:06 +0200, Arnd Bergmann wrote:
> The powerpc64 default configuration leads to warnings for the
> infiniband
> core code:
>
> infiniband/core/cma.c: In function 'cma_get_net_dev':
> infiniband/core/cma.c:1242:12: warning:
> 'src_addr_storage.sin_addr.s_addr' may be used uninitialized in this
> function [-Wmaybe-uninitialized]
>
> The code looks correct to me, and I don't see the warnings on the
> other architectures, so this is a dumb change to add an unneeded
> initialization to the variables in order to shut up the warning.
>
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
> Link: http://arm-soc.lixom.net/buildlogs/mainline/v4.7-
> rc6/buildall.powerpc.ppc64_defconfig.log.passed
I thought about taking this, but I also looked over the code and it
looks correct to me. This is a semi-hot path in the connection bring
up code, so I'm loathe to put in sizeof(struct sockaddr_storage) * 2 of
needless memory writes. So, I dropped this patch. Hopefully, ppc64
compiler will straighten its warnings out soon.
> ---
> drivers/infiniband/core/cma.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/infiniband/core/cma.c
> b/drivers/infiniband/core/cma.c
> index a3c9930f1f93..924ac237310b 100644
> --- a/drivers/infiniband/core/cma.c
> +++ b/drivers/infiniband/core/cma.c
> @@ -1309,7 +1309,7 @@ static bool validate_net_dev(struct net_device
> *net_dev,
> static struct net_device *cma_get_net_dev(struct ib_cm_event
> *ib_event,
> const struct cma_req_info
> *req)
> {
> - struct sockaddr_storage listen_addr_storage,
> src_addr_storage;
> + struct sockaddr_storage listen_addr_storage = {},
> src_addr_storage = {};
> struct sockaddr *listen_addr = (struct sockaddr
> *)&listen_addr_storage,
> *src_addr = (struct sockaddr
> *)&src_addr_storage;
> struct net_device *net_dev;
--
Doug Ledford <dledford@redhat.com>
GPG KeyID: 0E572FDD
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-08-02 18:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-04 15:06 [PATCH] infiniband: shut up a maybe-uninitialized warning Arnd Bergmann
2016-08-02 17:45 ` Doug Ledford [this message]
2016-08-02 20:05 ` Arnd Bergmann
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=1470159925.18081.21.camel@redhat.com \
--to=dledford@redhat.com \
--cc=arnd@arndb.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.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