From: Jakub Kicinski <kuba@kernel•org>
To: Xiao Liang <shaw.leon@gmail•com>
Cc: netdev@vger•kernel.org, linux-kselftest@vger•kernel.org,
Kuniyuki Iwashima <kuniyu@amazon•com>,
Donald Hunter <donald.hunter@gmail•com>,
"David S. Miller" <davem@davemloft•net>,
David Ahern <dsahern@kernel•org>,
Eric Dumazet <edumazet@google•com>,
Paolo Abeni <pabeni@redhat•com>, Ido Schimmel <idosch@nvidia•com>,
Andrew Lunn <andrew+netdev@lunn•ch>,
Simon Horman <horms@kernel•org>, Shuah Khan <shuah@kernel•org>,
Jiri Pirko <jiri@resnulli•us>, Hangbin Liu <liuhangbin@gmail•com>,
linux-rdma@vger•kernel.org, linux-can@vger•kernel.org,
osmocom-net-gprs@lists•osmocom.org, bpf@vger•kernel.org,
linux-ppp@vger•kernel.org, wireguard@lists•zx2c4.com,
linux-wireless@vger•kernel.org, b.a.t.m.a.n@lists•open-mesh.org,
bridge@lists•linux.dev, linux-wpan@vger•kernel.org,
linux-kernel@vger•kernel.org
Subject: Re: [PATCH net-next v4 0/5] net: Improve netns handling in RTNL and ip_tunnel
Date: Mon, 18 Nov 2024 19:07:00 -0800 [thread overview]
Message-ID: <20241118190700.4c1b8156@kernel.org> (raw)
In-Reply-To: <20241118143244.1773-1-shaw.leon@gmail.com>
On Mon, 18 Nov 2024 22:32:39 +0800 Xiao Liang wrote:
> This patch series includes some netns-related improvements and fixes for
> RTNL and ip_tunnel, to make link creation more intuitive:
>
> - Creating link in another net namespace doesn't conflict with link names
> in current one.
> - Refector rtnetlink link creation. Create link in target namespace
> directly. Pass both source and link netns to drivers via newlink()
> callback.
>
> So that
>
> # ip link add netns ns1 link-netns ns2 tun0 type gre ...
>
> will create tun0 in ns1, rather than create it in ns2 and move to ns1.
> And don't conflict with another interface named "tun0" in current netns.
## Form letter - net-next-closed
The merge window for v6.13 has begun and net-next is closed for new drivers,
features, code refactoring and optimizations. We are currently accepting
bug fixes only.
Please repost when net-next reopens after Dec 2nd.
RFC patches sent for review only are welcome at any time.
See: https://www.kernel.org/doc/html/next/process/maintainer-netdev.html#development-cycle
--
pw-bot: defer
prev parent reply other threads:[~2024-11-19 3:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-18 14:32 [PATCH net-next v4 0/5] net: Improve netns handling in RTNL and ip_tunnel Xiao Liang
2024-11-18 14:32 ` [PATCH net-next v4 1/5] net: ip_tunnel: Build flow in underlay net namespace Xiao Liang
2024-11-18 14:32 ` [PATCH net-next v4 2/5] rtnetlink: Lookup device in target netns when creating link Xiao Liang
2024-11-18 14:32 ` [PATCH net-next v4 3/5] rtnetlink: Decouple net namespaces in rtnl_newlink_create() Xiao Liang
2024-11-21 21:43 ` kernel test robot
2024-11-18 14:32 ` [PATCH net-next v4 4/5] selftests: net: Add python context manager for netns entering Xiao Liang
2024-11-18 14:32 ` [PATCH net-next v4 5/5] selftests: net: Add two test cases for link netns Xiao Liang
2024-11-19 3:07 ` Jakub Kicinski [this message]
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=20241118190700.4c1b8156@kernel.org \
--to=kuba@kernel$(echo .)org \
--cc=andrew+netdev@lunn$(echo .)ch \
--cc=b.a.t.m.a.n@lists$(echo .)open-mesh.org \
--cc=bpf@vger$(echo .)kernel.org \
--cc=bridge@lists$(echo .)linux.dev \
--cc=davem@davemloft$(echo .)net \
--cc=donald.hunter@gmail$(echo .)com \
--cc=dsahern@kernel$(echo .)org \
--cc=edumazet@google$(echo .)com \
--cc=horms@kernel$(echo .)org \
--cc=idosch@nvidia$(echo .)com \
--cc=jiri@resnulli$(echo .)us \
--cc=kuniyu@amazon$(echo .)com \
--cc=linux-can@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-kselftest@vger$(echo .)kernel.org \
--cc=linux-ppp@vger$(echo .)kernel.org \
--cc=linux-rdma@vger$(echo .)kernel.org \
--cc=linux-wireless@vger$(echo .)kernel.org \
--cc=linux-wpan@vger$(echo .)kernel.org \
--cc=liuhangbin@gmail$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=osmocom-net-gprs@lists$(echo .)osmocom.org \
--cc=pabeni@redhat$(echo .)com \
--cc=shaw.leon@gmail$(echo .)com \
--cc=shuah@kernel$(echo .)org \
--cc=wireguard@lists$(echo .)zx2c4.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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