All of lore.kernel.org
 help / color / mirror / Atom feed
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 v9 05/11] net: ip_tunnel: Use link netns in newlink() of rtnl_link_ops
Date: Thu, 13 Feb 2025 15:20:31 +0900	[thread overview]
Message-ID: <20250213062031.4547-1-kuniyu@amazon.com> (raw)
In-Reply-To: <20250210133002.883422-6-shaw.leon@gmail.com>

From: Xiao Liang <shaw.leon@gmail.com>
Date: Mon, 10 Feb 2025 21:29:56 +0800
> When link_net is set, use it as link netns instead of dev_net(). This
> prepares for rtnetlink core to create device in target netns directly,
> in which case the two namespaces may be different.
> 
> Convert common ip_tunnel_newlink() to accept an extra link netns
> argument. Don't overwrite ip_tunnel.net in ip_tunnel_init().

Why... ?  see a comment below.


[...]
> diff --git a/net/ipv4/ip_gre.c b/net/ipv4/ip_gre.c
> index 1fe9b13d351c..26d15f907551 100644
> --- a/net/ipv4/ip_gre.c
> +++ b/net/ipv4/ip_gre.c
> @@ -1413,7 +1413,8 @@ static int ipgre_newlink(struct net_device *dev,
>  	err = ipgre_netlink_parms(dev, data, tb, &p, &fwmark);
>  	if (err < 0)
>  		return err;
> -	return ip_tunnel_newlink(dev, tb, &p, fwmark);
> +	return ip_tunnel_newlink(params->link_net ? : dev_net(dev), dev, tb, &p,

This is duplicate at all call sites, let's move it into
ip_tunnel_newlink() by passing params.


> +				 fwmark);
>  }
>  
>  static int erspan_newlink(struct net_device *dev,
> 
> 
> diff --git a/net/ipv4/ip_tunnel.c b/net/ipv4/ip_tunnel.c
> index 09b73acf037a..618a50d5c0c2 100644
> --- a/net/ipv4/ip_tunnel.c
> +++ b/net/ipv4/ip_tunnel.c
> @@ -1213,11 +1213,11 @@ void ip_tunnel_delete_nets(struct list_head *net_list, unsigned int id,
>  }
>  EXPORT_SYMBOL_GPL(ip_tunnel_delete_nets);
>  
> -int ip_tunnel_newlink(struct net_device *dev, struct nlattr *tb[],
> -		      struct ip_tunnel_parm_kern *p, __u32 fwmark)
> +int ip_tunnel_newlink(struct net *net, struct net_device *dev,
> +		      struct nlattr *tb[], struct ip_tunnel_parm_kern *p,
> +		      __u32 fwmark)
>  {
>  	struct ip_tunnel *nt;
> -	struct net *net = dev_net(dev);
>  	struct ip_tunnel_net *itn;
>  	int mtu;
>  	int err;
> @@ -1326,7 +1326,9 @@ int ip_tunnel_init(struct net_device *dev)
>  	}
>  
>  	tunnel->dev = dev;
> -	tunnel->net = dev_net(dev);
> +	if (!tunnel->net)
> +		tunnel->net = dev_net(dev);

Isn't tunnel->net always non-NULL ?

ip_tunnel_newlink
-> netdev_priv(dev)->net = net
-> register_netdevice(dev)
  -> dev->netdev_ops->ndo_init(dev)
    -> ip_tunnel_init(dev)
      -> netdev_priv(dev)->net = dev_net(dev)

  reply	other threads:[~2025-02-13  6:20 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-10 13:29 [PATCH net-next v9 00/11] net: Improve netns handling in rtnetlink Xiao Liang
2025-02-10 13:29 ` [PATCH net-next v9 01/11] rtnetlink: Lookup device in target netns when creating link Xiao Liang
2025-02-10 13:29 ` [PATCH net-next v9 02/11] rtnetlink: Pack newlink() params into struct Xiao Liang
2025-02-13  6:53   ` Kuniyuki Iwashima
2025-02-13  8:36     ` Xiao Liang
2025-02-13  9:17       ` Paolo Abeni
2025-02-13 10:01         ` Xiao Liang
2025-02-10 13:29 ` [PATCH net-next v9 03/11] net: Use link netns in newlink() of rtnl_link_ops Xiao Liang
2025-02-13  6:55   ` Kuniyuki Iwashima
2025-02-10 13:29 ` [PATCH net-next v9 04/11] ieee802154: 6lowpan: Validate " Xiao Liang
2025-02-13  5:48   ` Kuniyuki Iwashima
2025-02-10 13:29 ` [PATCH net-next v9 05/11] net: ip_tunnel: Use " Xiao Liang
2025-02-13  6:20   ` Kuniyuki Iwashima [this message]
2025-02-13  8:27     ` Xiao Liang
2025-02-10 13:29 ` [PATCH net-next v9 06/11] net: ipv6: " Xiao Liang
2025-02-13  7:05   ` Kuniyuki Iwashima
2025-02-13  8:37     ` Xiao Liang
2025-02-13  9:55       ` Xiao Liang
2025-02-13 11:00         ` Kuniyuki Iwashima
2025-02-14  9:22           ` Xiao Liang
2025-02-14 10:51             ` Kuniyuki Iwashima
2025-02-10 13:29 ` [PATCH net-next v9 07/11] net: xfrm: " Xiao Liang
2025-02-10 13:29 ` [PATCH net-next v9 08/11] rtnetlink: Remove "net" from newlink params Xiao Liang
2025-02-10 13:30 ` [PATCH net-next v9 09/11] rtnetlink: Create link directly in target net namespace Xiao Liang
2025-02-10 13:30 ` [PATCH net-next v9 10/11] selftests: net: Add python context manager for netns entering Xiao Liang
2025-02-10 13:30 ` [PATCH net-next v9 11/11] selftests: net: Add test cases for link and peer netns Xiao Liang

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=20250213062031.4547-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.