infiniband build warning
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.
drivers/infiniband/core/cma.c +1 -1
@@ -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 ;
Signature · 2 lines
Michel "Walken" Lespinasse A program is never fully debugged until the last user dies.
Quoted 4 lines
I am seeing build warnings in
drivers/infiniband/core/cma.cstarting with v3.11-rc1. These can be reproduced with gcc 4.6.3.Would you consider applying the following fix ?
A patch to fix this was submitted to the linux-rdma list last week. Thanks.
- Sean
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
Quoted 5 lines · Sean
Quoted 3 lines
I am seeing build warnings in
drivers/infiniband/core/cma.cstarting with v3.11-rc1. These can be reproduced with gcc 4.6.3.
Would you consider applying the following fix ?A patch to fix this was submitted to the linux-rdma list last week.
Hi Roland,
There is a nice set of patches (IPoIB virtualization fixes, mlx5 fixes, iser patches to cope with Connect-IB no FMR, etc, etc) posted to linux-rdma little before && after 3.11-rc1 was out, and we are @ rc2 now. I think we need to get them upstreamed around this time such that its early enough in the cycle, makes sense?
Or.