netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* [PATCH v2 iproute2 0/2] iplink: Fix link-netns handling
@ 2024-10-11  8:01 Xiao Liang
  2024-10-11  8:01 ` [PATCH v2 iproute2 1/2] ip: Move of set_netnsid_from_name() to namespace.c Xiao Liang
                   ` (2 more replies)
  0 siblings, 3 replies; 7+ messages in thread
From: Xiao Liang @ 2024-10-11  8:01 UTC (permalink / raw)
  To: Stephen Hemminger, netdev

When handling something like:

    # ip -n ns1 link add netns ns2 link-netns ns3 link eth1 eth1.100 type vlan id 100

should lookup eth1 in ns3 and set IFLA_LINK_NETNSID to the id of ns3 from ns2.
But currently ip-link tries to find eth1 in ns1 and failes. This series fixes
it.

---

v2:
- Rebase in regard to
    57daf8ff8c6c ("iplink: fix fd leak when playing with netns")


Xiao Liang (2):
  ip: Move of set_netnsid_from_name() to namespace.c
  iplink: Fix link-netns id and link ifindex

 include/namespace.h |   2 +
 ip/ip_common.h      |   2 -
 ip/iplink.c         | 143 ++++++++++++++++++++++++++++++++++++--------
 ip/ipnetns.c        |  28 +--------
 lib/namespace.c     |  27 +++++++++
 5 files changed, 150 insertions(+), 52 deletions(-)

-- 
2.47.0


^ permalink raw reply	[flat|nested] 7+ messages in thread

end of thread, other threads:[~2024-10-17 19:20 UTC | newest]

Thread overview: 7+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2024-10-11  8:01 [PATCH v2 iproute2 0/2] iplink: Fix link-netns handling Xiao Liang
2024-10-11  8:01 ` [PATCH v2 iproute2 1/2] ip: Move of set_netnsid_from_name() to namespace.c Xiao Liang
2024-10-11  8:01 ` [PATCH v2 iproute2 2/2] iplink: Fix link-netns id and link ifindex Xiao Liang
2024-10-15  7:45   ` Nicolas Dichtel
2024-10-15  9:06     ` Xiao Liang
2024-10-15 14:27       ` Nicolas Dichtel
2024-10-17 19:20 ` [PATCH v2 iproute2 0/2] iplink: Fix link-netns handling patchwork-bot+netdevbpf

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).