From: Kuniyuki Iwashima <kuniyu@amazon.com>
To: <shaw.leon@gmail.com>
Cc: <davem@davemloft.net>, <dsahern@kernel.org>,
<edumazet@google.com>, <idosch@nvidia.com>, <kuba@kernel.org>,
<kuniyu@amazon.com>, <netdev@vger.kernel.org>,
<pabeni@redhat.com>
Subject: Re: [PATCH net-next 2/5] rtnetlink: Add netns_atomic flag in rtnl_link_ops
Date: Tue, 22 Oct 2024 21:03:16 -0700 [thread overview]
Message-ID: <20241023040316.28273-1-kuniyu@amazon.com> (raw)
In-Reply-To: <20241023023146.372653-3-shaw.leon@gmail.com>
From: Xiao Liang <shaw.leon@gmail.com>
Date: Wed, 23 Oct 2024 10:31:43 +0800
> Currently these two steps are needed to create a net device with
> IFLA_LINK_NETNSID attr:
>
> 1. create and setup the netdev in the link netns with
> rtnl_create_link()
> 2. move it to the target netns with dev_change_net_namespace()
IIRC, this is to send the notification in the link netns.
>
> This has some side effects, including extra ifindex allocation, ifname
> validation and link notifications in link netns.
>
> Add a netns_atomic flag, that if set to true, devices will be created in
> the target netns directly.
>
> Signed-off-by: Xiao Liang <shaw.leon@gmail.com>
> ---
> include/net/rtnetlink.h | 3 +++
> net/core/rtnetlink.c | 7 ++++---
> 2 files changed, 7 insertions(+), 3 deletions(-)
>
> diff --git a/include/net/rtnetlink.h b/include/net/rtnetlink.h
> index e0d9a8eae6b6..59594cef2272 100644
> --- a/include/net/rtnetlink.h
> +++ b/include/net/rtnetlink.h
> @@ -74,6 +74,8 @@ static inline int rtnl_msg_family(const struct nlmsghdr *nlh)
> * @srcu: Used internally
> * @kind: Identifier
> * @netns_refund: Physical device, move to init_net on netns exit
> + * @netns_atomic: Device can be created in target netns even when
> + * link-netns is different, avoiding netns change.
> * @maxtype: Highest device specific netlink attribute number
> * @policy: Netlink policy for device specific attribute validation
> * @validate: Optional validation function for netlink/changelink parameters
> @@ -115,6 +117,7 @@ struct rtnl_link_ops {
> void (*setup)(struct net_device *dev);
>
> bool netns_refund;
> + bool netns_atomic;
> unsigned int maxtype;
> const struct nla_policy *policy;
> int (*validate)(struct nlattr *tb[],
> diff --git a/net/core/rtnetlink.c b/net/core/rtnetlink.c
> index ff8d25acfc00..99250779d8ba 100644
> --- a/net/core/rtnetlink.c
> +++ b/net/core/rtnetlink.c
> @@ -3679,8 +3679,9 @@ static int rtnl_newlink_create(struct sk_buff *skb, struct ifinfomsg *ifm,
> name_assign_type = NET_NAME_ENUM;
> }
>
> - dev = rtnl_create_link(link_net ? : tgt_net, ifname,
> - name_assign_type, ops, tb, extack);
> + dev = rtnl_create_link(!link_net || ops->netns_atomic ?
> + tgt_net : link_net, ifname, name_assign_type,
> + ops, tb, extack);
> if (IS_ERR(dev)) {
> err = PTR_ERR(dev);
> goto out;
> @@ -3700,7 +3701,7 @@ static int rtnl_newlink_create(struct sk_buff *skb, struct ifinfomsg *ifm,
> err = rtnl_configure_link(dev, ifm, portid, nlh);
> if (err < 0)
> goto out_unregister;
> - if (link_net) {
> + if (link_net && !ops->netns_atomic) {
> err = dev_change_net_namespace(dev, tgt_net, ifname);
> if (err < 0)
> goto out_unregister;
> --
> 2.47.0
>
next prev parent reply other threads:[~2024-10-23 4:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-23 2:31 [PATCH net-next 0/5] net: Improve netns handling in RTNL and ip_tunnel Xiao Liang
2024-10-23 2:31 ` [PATCH net-next 1/5] rtnetlink: Lookup device in target netns when creating link Xiao Liang
2024-10-23 3:49 ` Kuniyuki Iwashima
2024-10-23 4:19 ` Xiao Liang
2024-10-23 2:31 ` [PATCH net-next 2/5] rtnetlink: Add netns_atomic flag in rtnl_link_ops Xiao Liang
2024-10-23 4:03 ` Kuniyuki Iwashima [this message]
2024-10-23 4:36 ` Xiao Liang
2024-10-23 2:31 ` [PATCH net-next 3/5] net: ip_tunnel: Build flow in underlay net namespace Xiao Liang
2024-10-23 2:31 ` [PATCH net-next 4/5] net: ip_tunnel: Add source netns support for newlink Xiao Liang
2024-10-23 2:31 ` [PATCH net-next 5/5] net: ip_gre: Add netns_atomic module parameter Xiao Liang
2024-10-29 23:17 ` [PATCH net-next 0/5] net: Improve netns handling in RTNL and ip_tunnel Jakub Kicinski
2024-10-30 2:10 ` Xiao Liang
2024-10-30 23:35 ` Jakub Kicinski
2024-10-31 3:08 ` Xiao Liang
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=20241023040316.28273-1-kuniyu@amazon.com \
--to=kuniyu@amazon.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=idosch@nvidia.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shaw.leon@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;
as well as URLs for NNTP newsgroup(s).