From: Ido Schimmel <idosch@nvidia.com>
To: Kuniyuki Iwashima <kuniyu@google.com>
Cc: "David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
David Ahern <dsahern@kernel.org>, Simon Horman <horms@kernel.org>,
Steffen Klassert <steffen.klassert@secunet.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
Kuniyuki Iwashima <kuni1840@gmail.com>,
netdev@vger.kernel.org
Subject: Re: [PATCH v3 net-next 0/7] ip_tunnel: Support per-netns device unregistration.
Date: Mon, 14 Sep 2026 13:15:54 +0300 [thread overview]
Message-ID: <20260914101554.GA245219@shredder> (raw)
In-Reply-To: <20260912230043.2586313-1-kuniyu@google.com>
On Sat, Sep 12, 2026 at 11:00:26PM +0000, Kuniyuki Iwashima wrote:
> Patch 1 - 3 are prep patches to unlink ip_tunnel device from
> the hash table in ip_tunnel_dellink() only.
>
> Patch 4 removes ip_tunnel_del() from ip_tunnel_uninit() to
> ip_tunnel_dellink().
>
> Patch 5 & 6 adds mutex to protect the per-netns hash table.
>
> Patch 7 uses unregister_netdevice_queue_net() to support
> cross-netns device unregistration.
Reviewed-by: Ido Schimmel <idosch@nvidia.com>
>
>
> Changes:
> v3:
> * Patch 7
> * Check check_net(t->net) in ip_tunnel_ctl().
Thanks!
next prev parent reply other threads:[~2026-09-14 10:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-12 23:00 [PATCH v3 net-next 0/7] ip_tunnel: Support per-netns device unregistration Kuniyuki Iwashima
2026-09-12 23:00 ` [PATCH v3 net-next 1/7] ipmr: Call ->dellink() to remove DVMRP tunnel device Kuniyuki Iwashima
2026-09-12 23:00 ` [PATCH v3 net-next 2/7] ip_tunnel: Set itn->fb_tunnel_dev to NULL in ip_tunnel_delete_net() Kuniyuki Iwashima
2026-09-12 23:00 ` [PATCH v3 net-next 3/7] ip_tunnel: Don't pass rtnl_link_ops to ip_tunnel_delete_net() Kuniyuki Iwashima
2026-09-12 23:00 ` [PATCH v3 net-next 4/7] ip_tunnel: Centralise ip_tunnel_del() to ip_tunnel_dellink() Kuniyuki Iwashima
2026-09-12 23:00 ` [PATCH v3 net-next 5/7] ip_tunnel: Unify error paths in ip_tunnel_newlink() and ip_tunnel_changelink() Kuniyuki Iwashima
2026-09-12 23:00 ` [PATCH v3 net-next 6/7] ip_tunnel: Protect ip_tunnel_net.tunnels[] with mutex Kuniyuki Iwashima
2026-09-12 23:00 ` [PATCH v3 net-next 7/7] ip_tunnel: Support per-netns device unregistration Kuniyuki Iwashima
2026-09-14 10:15 ` Ido Schimmel [this message]
2026-09-15 11:30 ` [PATCH v3 net-next 0/7] " 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=20260914101554.GA245219@shredder \
--to=idosch@nvidia.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=herbert@gondor.apana.org.au \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=kuni1840@gmail.com \
--cc=kuniyu@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=steffen.klassert@secunet.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