Re: [PATCH net-next v4 0/5] net: Improve netns handling in RTNL and ip_tunnel
Jakub Kicinski <[email protected]>
| Newsgroups | gmane.linux.can,gmane.linux.network,gmane.linux.drivers.rdma,gmane.linux.kernel.bpf,gmane.linux.ppp,gmane.network.wireguard,gmane.linux.kernel.wireless.general,gmane.org.freifunk.batman,gmane.linux.kernel |
|---|---|
| Message-ID | <[email protected]> |
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