[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250212084519.38648-1-kuniyu@amazon.com>
Date: Wed, 12 Feb 2025 17:45:19 +0900
From: Kuniyuki Iwashima <kuniyu@...zon.com>
To: <bastien.curutchet@...tlin.com>
CC: <alexis.lothore@...tlin.com>, <davem@...emloft.net>,
<edumazet@...gle.com>, <horms@...nel.org>, <kuba@...nel.org>,
<kuniyu@...zon.com>, <linux-kernel@...r.kernel.org>,
<netdev@...r.kernel.org>, <pabeni@...hat.com>, <razor@...ckwall.org>,
<stable@...r.kernel.org>, <thomas.petazzoni@...tlin.com>
Subject: Re: [PATCH net 1/2] rtnetlink: Fix rtnl_net_cmp_locks() when DEBUG is off
From: "Bastien Curutchet (eBPF Foundation)" <bastien.curutchet@...tlin.com>
Date: Wed, 12 Feb 2025 09:23:47 +0100
> rtnl_net_cmp_locks() always returns -1 if CONFIG_DEBUG_NET_SMALL_RTNL is
> disabled. However, if CONFIG_DEBUG_NET_SMALL_RTNL is enabled, it returns 0
> when both inputs are equal. It is then used by rtnl_nets_add() to call
> put_net() if the net to be added is already present in the struct
> rtnl_nets. As a result, when rtnl_nets_add() is called on an already
> present net, put_net() is called only if DEBUG is on.
If CONFIG_DEBUG_NET_SMALL_RTNL is disabled, every duplicate net is
added to rtnl_nets, so put_net() is expected to be called for each
in rtnl_nets_destroy().
Powered by blists - more mailing lists