From: Zhu Yanjun <yanjun.zhu@linux.dev>
To: jgg@ziepe.ca, leon@kernel.org, zyjzyj2000@gmail.com,
shuah@kernel.org, linux-rdma@vger.kernel.org,
linux-kselftest@vger.kernel.org, dsahern@kernel.org
Cc: Zhu Yanjun <yanjun.zhu@linux.dev>
Subject: [PATCH v5 1/4] RDMA/nldev: Add dellink function pointer
Date: Tue, 10 Mar 2026 03:05:15 +0100 [thread overview]
Message-ID: <20260310020519.101415-2-yanjun.zhu@linux.dev> (raw)
In-Reply-To: <20260310020519.101415-1-yanjun.zhu@linux.dev>
The newlink function pointer is added. And the sock listening on port 4791
is added in the newlink function. So the dellink function is needed to
remove the sock.
Signed-off-by: Zhu Yanjun <yanjun.zhu@linux.dev>
---
drivers/infiniband/core/nldev.c | 6 ++++++
include/rdma/rdma_netlink.h | 2 ++
2 files changed, 8 insertions(+)
diff --git a/drivers/infiniband/core/nldev.c b/drivers/infiniband/core/nldev.c
index 2220a2dfab24..48684930660a 100644
--- a/drivers/infiniband/core/nldev.c
+++ b/drivers/infiniband/core/nldev.c
@@ -1824,6 +1824,12 @@ static int nldev_dellink(struct sk_buff *skb, struct nlmsghdr *nlh,
return -EINVAL;
}
+ if (device->link_ops) {
+ err = device->link_ops->dellink(device);
+ if (err)
+ return err;
+ }
+
ib_unregister_device_and_put(device);
return 0;
}
diff --git a/include/rdma/rdma_netlink.h b/include/rdma/rdma_netlink.h
index 326deaf56d5d..2fd1358ea57d 100644
--- a/include/rdma/rdma_netlink.h
+++ b/include/rdma/rdma_netlink.h
@@ -5,6 +5,7 @@
#include <linux/netlink.h>
#include <uapi/rdma/rdma_netlink.h>
+#include <rdma/ib_verbs.h>
struct ib_device;
@@ -126,6 +127,7 @@ struct rdma_link_ops {
struct list_head list;
const char *type;
int (*newlink)(const char *ibdev_name, struct net_device *ndev);
+ int (*dellink)(struct ib_device *dev);
};
void rdma_link_register(struct rdma_link_ops *ops);
--
2.53.0
next prev parent reply other threads:[~2026-03-10 2:05 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-10 2:05 [PATCH v5 0/4] RDMA/rxe: Add the support that rxe can work in net namespace Zhu Yanjun
2026-03-10 2:05 ` Zhu Yanjun [this message]
2026-03-10 15:47 ` [PATCH v5 1/4] RDMA/nldev: Add dellink function pointer David Ahern
2026-03-10 19:01 ` Leon Romanovsky
2026-03-11 1:58 ` Yanjun.Zhu
2026-03-11 8:54 ` Leon Romanovsky
2026-03-11 22:01 ` Yanjun.Zhu
2026-03-11 22:09 ` Yanjun.Zhu
2026-03-12 2:04 ` David Ahern
2026-03-12 3:59 ` Zhu Yanjun
2026-03-12 5:09 ` Zhu Yanjun
2026-03-12 18:04 ` Yanjun.Zhu
2026-03-10 2:05 ` [PATCH v5 2/4] RDMA/rxe: Add net namespace support for IPv4/IPv6 sockets Zhu Yanjun
2026-03-10 15:48 ` David Ahern
2026-03-10 2:05 ` [PATCH v5 3/4] RDMA/rxe: Support RDMA link creation and destruction per net namespace Zhu Yanjun
2026-03-10 15:48 ` David Ahern
2026-03-10 18:57 ` Leon Romanovsky
2026-03-10 20:32 ` Yanjun.Zhu
2026-03-11 8:45 ` Leon Romanovsky
2026-03-11 19:08 ` Yanjun.Zhu
2026-03-10 2:05 ` [PATCH v5 4/4] RDMA/rxe: Add testcase for net namespace rxe Zhu Yanjun
2026-03-10 15:49 ` David Ahern
2026-03-10 18:53 ` Leon Romanovsky
2026-03-10 21:01 ` Yanjun.Zhu
2026-03-11 8:51 ` Leon Romanovsky
2026-03-11 22:51 ` Yanjun.Zhu
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=20260310020519.101415-2-yanjun.zhu@linux.dev \
--to=yanjun.zhu@linux.dev \
--cc=dsahern@kernel.org \
--cc=jgg@ziepe.ca \
--cc=leon@kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=shuah@kernel.org \
--cc=zyjzyj2000@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox