Håkon Bugge a242c36951 RDMA/netlink: Do not always generate an ACK for some netlink operations
In rdma_nl_rcv_skb(), the local variable err is assigned the return value
of the supplied callback function, which could be one of
ib_nl_handle_resolve_resp(), ib_nl_handle_set_timeout(), or
ib_nl_handle_ip_res_resp(). These three functions all return skb->len on
success.

rdma_nl_rcv_skb() is merely a copy of netlink_rcv_skb(). The callback
functions used by the latter have the convention: "Returns 0 on success or
a negative error code".

In particular, the statement (equal for both functions):

   if (nlh->nlmsg_flags & NLM_F_ACK || err)

implies that rdma_nl_rcv_skb() always will ack a message, independent of
the NLM_F_ACK being set in nlmsg_flags or not.

The fix could be to change the above statement, but it is better to keep
the two *_rcv_skb() functions equal in this respect and instead change the
three callback functions in the rdma subsystem to the correct convention.

Fixes: 2ca546b92a02 ("IB/sa: Route SA pathrecord query through netlink")
Fixes: ae43f8286730 ("IB/core: Add IP to GID netlink offload")
Link: https://lore.kernel.org/r/20191216120436.3204814-1-haakon.bugge@oracle.com
Suggested-by: Mark Haywood <mark.haywood@oracle.com>
Signed-off-by: Håkon Bugge <haakon.bugge@oracle.com>
Tested-by: Mark Haywood <mark.haywood@oracle.com>
Reviewed-by: Leon Romanovsky <leonro@mellanox.com>
Reviewed-by: Jason Gunthorpe <jgg@mellanox.com>
Signed-off-by: Jason Gunthorpe <jgg@mellanox.com>
2020-01-03 16:02:32 -04:00
..
2019-12-27 11:09:04 -08:00
2019-12-20 10:11:30 -08:00
2019-12-01 18:43:25 -08:00
2019-11-22 11:16:26 +05:30
2019-12-27 11:02:48 -08:00
2019-12-10 23:15:09 +01:00
2019-12-20 10:42:25 -08:00
2019-12-03 13:58:22 -08:00
2019-11-30 14:35:43 -08:00
2019-12-01 18:42:02 -08:00
2019-12-13 14:27:19 -08:00
2019-12-09 10:36:44 -08:00
2019-12-06 08:28:51 -08:00
2019-12-03 13:58:22 -08:00
2019-12-03 14:37:12 -08:00
2019-12-21 06:17:05 -08:00
2019-12-03 14:09:14 -08:00
2019-12-01 18:43:25 -08:00
2019-12-13 14:27:19 -08:00
2019-12-05 11:43:31 -08:00
2019-11-25 19:40:40 -08:00
2019-12-05 11:43:31 -08:00
2019-12-13 15:42:09 -08:00
2019-12-05 11:28:14 -08:00
2019-12-17 13:08:41 -08:00
2019-12-01 18:39:24 -08:00
2019-12-03 13:31:08 -08:00
2019-12-22 10:36:55 -08:00
2019-12-27 17:28:41 -08:00
2019-12-17 13:06:31 -08:00
2019-12-27 17:28:41 -08:00
2019-12-05 13:18:54 -08:00
2019-12-07 14:51:04 -08:00
2019-12-03 13:58:22 -08:00
2019-11-14 13:06:33 +08:00
2019-12-01 18:01:03 -08:00
2019-12-21 06:24:56 -08:00