From: Kuniyuki Iwashima <kuniyu@amazon.com>
To: <shaw.leon@gmail.com>
Cc: <alex.aring@gmail.com>, <andrew+netdev@lunn.ch>,
<b.a.t.m.a.n@lists.open-mesh.org>, <bpf@vger.kernel.org>,
<bridge@lists.linux.dev>, <davem@davemloft.net>,
<donald.hunter@gmail.com>, <dsahern@kernel.org>,
<edumazet@google.com>, <herbert@gondor.apana.org.au>,
<horms@kernel.org>, <kuba@kernel.org>, <kuniyu@amazon.com>,
<linux-can@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-kselftest@vger.kernel.org>, <linux-ppp@vger.kernel.org>,
<linux-rdma@vger.kernel.org>, <linux-wireless@vger.kernel.org>,
<linux-wpan@vger.kernel.org>, <miquel.raynal@bootlin.com>,
<netdev@vger.kernel.org>, <osmocom-net-gprs@lists.osmocom.org>,
<pabeni@redhat.com>, <shuah@kernel.org>,
<stefan@datenfreihafen.org>, <steffen.klassert@secunet.com>,
<wireguard@lists.zx2c4.com>
Subject: Re: [PATCH net-next v10 02/13] rtnetlink: Pack newlink() params into struct
Date: Thu, 20 Feb 2025 19:24:49 -0800 [thread overview]
Message-ID: <20250221032449.73597-1-kuniyu@amazon.com> (raw)
In-Reply-To: <20250219125039.18024-3-shaw.leon@gmail.com>
From: Xiao Liang <shaw.leon@gmail.com>
Date: Wed, 19 Feb 2025 20:50:28 +0800
> There are 4 net namespaces involved when creating links:
>
> - source netns - where the netlink socket resides,
> - target netns - where to put the device being created,
> - link netns - netns associated with the device (backend),
> - peer netns - netns of peer device.
>
> Currently, two nets are passed to newlink() callback - "src_net"
> parameter and "dev_net" (implicitly in net_device). They are set as
> follows, depending on netlink attributes in the request.
>
> +------------+-------------------+---------+---------+
> | peer netns | IFLA_LINK_NETNSID | src_net | dev_net |
> +------------+-------------------+---------+---------+
> | | absent | source | target |
> | absent +-------------------+---------+---------+
> | | present | link | link |
> +------------+-------------------+---------+---------+
> | | absent | peer | target |
> | present +-------------------+---------+---------+
> | | present | peer | link |
> +------------+-------------------+---------+---------+
>
> When IFLA_LINK_NETNSID is present, the device is created in link netns
> first and then moved to target netns. This has some side effects,
> including extra ifindex allocation, ifname validation and link events.
> These could be avoided if we create it in target netns from
> the beginning.
>
> On the other hand, the meaning of src_net parameter is ambiguous. It
> varies depending on how parameters are passed. It is the effective
> link (or peer netns) by design, but some drivers ignore it and use
> dev_net instead.
>
> To provide more netns context for drivers, this patch packs existing
> newlink() parameters, along with the source netns, link netns and peer
> netns, into a struct. The old "src_net" is renamed to "net" to avoid
> confusion with real source netns, and will be deprecated later. The use
> of src_net are converted to params->net trivially.
>
> Signed-off-by: Xiao Liang <shaw.leon@gmail.com>
Reviewed-by: Kuniyuki Iwashima <kuniyu@amazon.com>
next prev parent reply other threads:[~2025-02-21 3:25 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-19 12:50 [PATCH net-next v10 00/13] net: Improve netns handling in rtnetlink Xiao Liang
2025-02-19 12:50 ` [PATCH net-next v10 01/13] rtnetlink: Lookup device in target netns when creating link Xiao Liang
2025-02-19 12:50 ` [PATCH net-next v10 02/13] rtnetlink: Pack newlink() params into struct Xiao Liang
2025-02-21 3:24 ` Kuniyuki Iwashima [this message]
2025-02-19 12:50 ` [PATCH net-next v10 03/13] net: Use link/peer netns in newlink() of rtnl_link_ops Xiao Liang
2025-02-19 12:50 ` [PATCH net-next v10 04/13] ieee802154: 6lowpan: Validate link " Xiao Liang
2025-02-19 12:50 ` [PATCH net-next v10 05/13] net: ip_tunnel: Don't set tunnel->net in ip_tunnel_init() Xiao Liang
2025-02-21 3:26 ` Kuniyuki Iwashima
2025-02-19 12:50 ` [PATCH net-next v10 06/13] net: ip_tunnel: Use link netns in newlink() of rtnl_link_ops Xiao Liang
2025-02-21 3:35 ` Kuniyuki Iwashima
2025-02-19 12:50 ` [PATCH net-next v10 07/13] net: ipv6: Init tunnel link-netns before registering dev Xiao Liang
2025-02-21 4:06 ` Kuniyuki Iwashima
2025-02-21 7:34 ` Xiao Liang
2025-02-19 12:50 ` [PATCH net-next v10 08/13] net: ipv6: Use link netns in newlink() of rtnl_link_ops Xiao Liang
2025-02-21 4:08 ` Kuniyuki Iwashima
2025-02-19 12:50 ` [PATCH net-next v10 09/13] net: xfrm: " Xiao Liang
2025-02-21 4:10 ` Kuniyuki Iwashima
2025-02-19 12:50 ` [PATCH net-next v10 10/13] rtnetlink: Remove "net" from newlink params Xiao Liang
2025-02-21 4:11 ` Kuniyuki Iwashima
2025-02-19 12:50 ` [PATCH net-next v10 11/13] rtnetlink: Create link directly in target net namespace Xiao Liang
2025-02-21 4:16 ` Kuniyuki Iwashima
2025-02-19 12:50 ` [PATCH net-next v10 12/13] selftests: net: Add python context manager for netns entering Xiao Liang
2025-02-19 12:50 ` [PATCH net-next v10 13/13] selftests: net: Add test cases for link and peer netns Xiao Liang
2025-02-21 23:47 ` [PATCH net-next v10 00/13] net: Improve netns handling in rtnetlink Jakub Kicinski
2025-02-21 23:50 ` patchwork-bot+netdevbpf
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=20250221032449.73597-1-kuniyu@amazon.com \
--to=kuniyu@amazon.com \
--cc=alex.aring@gmail.com \
--cc=andrew+netdev@lunn.ch \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=bpf@vger.kernel.org \
--cc=bridge@lists.linux.dev \
--cc=davem@davemloft.net \
--cc=donald.hunter@gmail.com \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=herbert@gondor.apana.org.au \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-ppp@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linux-wpan@vger.kernel.org \
--cc=miquel.raynal@bootlin.com \
--cc=netdev@vger.kernel.org \
--cc=osmocom-net-gprs@lists.osmocom.org \
--cc=pabeni@redhat.com \
--cc=shaw.leon@gmail.com \
--cc=shuah@kernel.org \
--cc=stefan@datenfreihafen.org \
--cc=steffen.klassert@secunet.com \
--cc=wireguard@lists.zx2c4.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).