From: Geliang Tang <geliangtang@gmail.com>
To: mptcp@lists.linux.dev
Cc: Geliang Tang <geliangtang@gmail.com>
Subject: [MPTCP][PATCH mptcp-next 4/9] mptcp: register ipv4 addr notifier
Date: Fri, 9 Jul 2021 19:04:31 +0800 [thread overview]
Message-ID: <3a4cae1a5964f864bc7cb74d311c014cda279a2a.1625825505.git.geliangtang@gmail.com> (raw)
In-Reply-To: <8b000137623aa94ab4f7c6b883c2003d91f3d147.1625825505.git.geliangtang@gmail.com>
This patch registered a ipv4 addr notifier, named mptcp_pm_addr4_notifier,
to deal with the events of net device UP, DOWN and CHANGE, and skip the
loopback device.
Save the ipv4 address, and pass it to the event handler.
Signed-off-by: Geliang Tang <geliangtang@gmail.com>
---
net/mptcp/pm_fullmesh.c | 49 +++++++++++++++++++++++++++++++++++++++++
1 file changed, 49 insertions(+)
diff --git a/net/mptcp/pm_fullmesh.c b/net/mptcp/pm_fullmesh.c
index b27f13a031e3..7c2d2b23fac3 100644
--- a/net/mptcp/pm_fullmesh.c
+++ b/net/mptcp/pm_fullmesh.c
@@ -3,6 +3,7 @@
#define pr_fmt(fmt) "MPTCP: " fmt
#include <linux/kernel.h>
+#include <linux/inetdevice.h>
#include <net/tcp.h>
#include <net/netns/generic.h>
#include <net/mptcp.h>
@@ -130,6 +131,45 @@ void mptcp_pm_fm_data_init(struct mptcp_sock *msk)
WRITE_ONCE(pm->accept_subflow, MPTCP_PM_FM_MAX_ADDR);
}
+static int mptcp_fm_cmd_mod_addr(struct net *net, const struct mptcp_addr_info *addr)
+{
+ return 0;
+}
+
+static void addr_event_handler(unsigned long event, struct net *net,
+ struct mptcp_addr_info *addr)
+{
+ if (event == NETDEV_CHANGE)
+ mptcp_fm_cmd_mod_addr(net, addr);
+}
+
+static int mptcp_pm_addr4_event(struct notifier_block *this,
+ unsigned long event, void *ptr)
+{
+ const struct in_ifaddr *ifa = (struct in_ifaddr *)ptr;
+ struct net *net = dev_net(ifa->ifa_dev->dev);
+ struct mptcp_addr_info addr = { 0 };
+
+ if (!(event == NETDEV_UP || event == NETDEV_DOWN || event == NETDEV_CHANGE))
+ goto out;
+
+ if (ifa->ifa_scope > RT_SCOPE_LINK ||
+ ipv4_is_loopback(ifa->ifa_local))
+ goto out;
+
+ addr.family = AF_INET;
+ addr.addr.s_addr = ifa->ifa_local;
+
+ addr_event_handler(event, net, &addr);
+
+out:
+ return NOTIFY_DONE;
+}
+
+static struct notifier_block mptcp_pm_addr4_notifier = {
+ .notifier_call = mptcp_pm_addr4_event,
+};
+
static int __net_init pm_fm_init_net(struct net *net)
{
struct pm_fm_pernet *pernet = net_generic(net, pm_fm_pernet_id);
@@ -177,4 +217,13 @@ void __init mptcp_pm_fm_init(void)
ret = register_pernet_subsys(&mptcp_pm_fm_pernet_ops);
if (ret)
return;
+
+ ret = register_inetaddr_notifier(&mptcp_pm_addr4_notifier);
+ if (ret)
+ goto err_reg_inetaddr;
+
+ return;
+
+err_reg_inetaddr:
+ unregister_pernet_subsys(&mptcp_pm_fm_pernet_ops);
}
--
2.31.1
next prev parent reply other threads:[~2021-07-09 11:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-09 11:04 [MPTCP][PATCH mptcp-next 0/9] fullmesh path manager support Geliang Tang
2021-07-09 11:04 ` [MPTCP][PATCH mptcp-next 1/9] mptcp: add a new sysctl path_manager Geliang Tang
2021-07-09 11:04 ` [MPTCP][PATCH mptcp-next 2/9] mptcp: add fullmesh path manager Geliang Tang
2021-07-09 11:04 ` [MPTCP][PATCH mptcp-next 3/9] mptcp: add fullmesh worker Geliang Tang
2021-07-09 11:04 ` Geliang Tang [this message]
2021-07-09 11:04 ` [MPTCP][PATCH mptcp-next 5/9] mptcp: register ipv6 addr notifier Geliang Tang
2021-07-09 11:04 ` [MPTCP][PATCH mptcp-next 6/9] mptcp: add netdev up event handler Geliang Tang
2021-07-09 11:04 ` [MPTCP][PATCH mptcp-next 7/9] mptcp: add netdev down " Geliang Tang
2021-07-09 11:04 ` [MPTCP][PATCH mptcp-next 8/9] mptcp: add proc file mptcp_fullmesh Geliang Tang
2021-07-09 11:04 ` [MPTCP][PATCH mptcp-next 9/9] selftests: mptcp: add fullmesh testcases Geliang Tang
2021-07-13 0:04 ` [MPTCP][PATCH mptcp-next 0/9] fullmesh path manager support Mat Martineau
2021-07-16 17:28 ` Paolo Abeni
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=3a4cae1a5964f864bc7cb74d311c014cda279a2a.1625825505.git.geliangtang@gmail.com \
--to=geliangtang@gmail.com \
--cc=mptcp@lists.linux.dev \
/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;
as well as URLs for NNTP newsgroup(s).