lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Message-Id: <1423667204-8807-4-git-send-email-raindel@mellanox.com> Date: Wed, 11 Feb 2015 17:06:37 +0200 From: Shachar Raindel <raindel@...lanox.com> To: roland@...nel.org, sean.hefty@...el.com Cc: linux-rdma@...r.kernel.org, netdev@...r.kernel.org, liranl@...lanox.com, guysh@...lanox.com, haggaie@...lanox.com, yotamke@...lanox.com, raindel@...lanox.com Subject: [PATCH v1 03/10] IB/core: Find the network namespace matching connection parameters From: Yotam Kenneth <yotamke@...lanox.com> In the case of IPoIB, and maybe in other cases, the network device is managed by an upper-layer protocol (ULP). In order to expose this network device to other users of the IB device, let ULPs implement a callback that returns network device according to connection parameters. The IB device and port, together with the P_Key and the IP address should be enough to uniquely identify the ULP net device. This function is passed to ib_core as part of the ib_client registration. Using this functionality, add a way to get the network namespace corresponding to a work completion. This is needed so that responses to CM requests can be sent from the same network namespace as the request. Signed-off-by: Haggai Eran <haggaie@...lanox.com> Signed-off-by: Yotam Kenneth <yotamke@...lanox.com> Signed-off-by: Shachar Raindel <raindel@...lanox.com> Signed-off-by: Guy Shapiro <guysh@...lanox.com> --- drivers/infiniband/core/device.c | 57 ++++++++++++++++++++++++++++++++++++++++ include/rdma/ib_verbs.h | 29 ++++++++++++++++++++ 2 files changed, 86 insertions(+) diff --git a/drivers/infiniband/core/device.c b/drivers/infiniband/core/device.c index 18c1ece..2f06be5 100644 --- a/drivers/infiniband/core/device.c +++ b/drivers/infiniband/core/device.c @@ -38,6 +38,7 @@ #include <linux/slab.h> #include <linux/init.h> #include <linux/mutex.h> +#include <linux/netdevice.h> #include <rdma/rdma_netlink.h> #include "core_priv.h" @@ -733,6 +734,62 @@ int ib_find_pkey(struct ib_device *device, } EXPORT_SYMBOL(ib_find_pkey); +static struct net_device *ib_get_net_dev_by_port_pkey_ip(struct ib_device *dev, + u8 port, + u16 pkey, + struct sockaddr *addr) +{ + struct net_device *ret = NULL; + struct ib_client *client; + + mutex_lock(&device_mutex); + list_for_each_entry(client, &client_list, list) + if (client->get_net_device_by_port_pkey_ip) { + ret = client->get_net_device_by_port_pkey_ip(dev, port, + pkey, + addr); + if (ret) + break; + } + + mutex_unlock(&device_mutex); + return ret; +} + +struct net *ib_get_net_ns_by_port_pkey_ip(struct ib_device *dev, + u8 port, + u16 pkey, + struct sockaddr *addr) +{ + struct net_device *ndev = NULL; + struct net *ns; + + switch (rdma_port_get_link_layer(dev, port)) { + case IB_LINK_LAYER_INFINIBAND: + if (!addr) + goto not_found; + ndev = ib_get_net_dev_by_port_pkey_ip(dev, port, pkey, addr); + break; + default: + goto not_found; + } + + if (!ndev) + goto not_found; + + rcu_read_lock(); + ns = maybe_get_net(dev_net(ndev)); + dev_put(ndev); + rcu_read_unlock(); + if (!ns) + goto not_found; + return ns; + +not_found: + return get_net(&init_net); +} +EXPORT_SYMBOL(ib_get_net_ns_by_port_pkey_ip); + static int __init ib_core_init(void) { int ret; diff --git a/include/rdma/ib_verbs.h b/include/rdma/ib_verbs.h index f4a85de..74b2394 100644 --- a/include/rdma/ib_verbs.h +++ b/include/rdma/ib_verbs.h @@ -1683,6 +1683,21 @@ struct ib_client { void (*add) (struct ib_device *); void (*remove)(struct ib_device *); + /* Returns the net_dev belonging to this ib_client and matching the + * given parameters. + * @dev: An RDMA device that the net_dev use for communication. + * @port: A physical port number on the RDMA device. + * @pkey: P_Key that the net_dev uses if applicable. + * @addr: An IP address the net_dev is configured with. + * + * An ib_client that implements a net_dev on top of RDMA devices + * (such as IP over IB) should implement this callback, allowing the + * rdma_cm module to find the right net_dev for a given request. */ + struct net_device *(*get_net_device_by_port_pkey_ip)( + struct ib_device *dev, + u8 port, + u16 pkey, + struct sockaddr *addr); struct list_head list; }; @@ -2679,4 +2694,18 @@ static inline int ib_check_mr_access(int flags) int ib_check_mr_status(struct ib_mr *mr, u32 check_mask, struct ib_mr_status *mr_status); +/** + * ib_get_net_ns_by_port_pkey_ip() - Return the appropriate net namespace + * for a received CM request + * @dev: An RDMA device on which the request has been received. + * @port: Port number on the RDMA device. + * @pkey: The Pkey the request came on. + * @addr: Contains the IP address that the request specified as its + * destination. + */ +struct net *ib_get_net_ns_by_port_pkey_ip(struct ib_device *dev, + u8 port, + u16 pkey, + struct sockaddr *addr); + #endif /* IB_VERBS_H */ -- 1.7.11.2 -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists