The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Antoine Tenart <atenart@kernel.org>
To: Tariq Toukan <tariqt@nvidia.com>
Cc: Andrew Lunn <andrew+netdev@lunn.ch>,
	 "David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	 Jakub Kicinski <kuba@kernel.org>,
	netdev@vger.kernel.org, Paolo Abeni <pabeni@redhat.com>,
	 Gal Pressman <gal@nvidia.com>, Jiri Pirko <jiri@nvidia.com>,
	Jiri Pirko <jiri@resnulli.us>,
	 linux-kernel@vger.kernel.org, Or Har-Toov <ohartoov@nvidia.com>,
	 Simon Horman <horms@kernel.org>
Subject: Re: [PATCH net] devlink: fix net namespace reference leak in reload
Date: Wed, 29 Jul 2026 12:23:40 +0200	[thread overview]
Message-ID: <amnUeT6MHSNvnM_b@kwain> (raw)
In-Reply-To: <20260729080600.2427721-1-tariqt@nvidia.com>

On Wed, Jul 29, 2026 at 11:06:00AM +0300, Tariq Toukan wrote:
> From: Or Har-Toov <ohartoov@nvidia.com>
> 
> devlink_nl_reload_doit() calls devlink_netns_get(), which returns a net
> with a held reference. When the requested namespace differs from the
> current one and the reload action is not DRIVER_REINIT, the function
> returns -EOPNOTSUPP without releasing the reference. Add the missing
> put_net() on this error path.
> 
> Fixes: 2edd92570441 ("devlink: don't allow to change net namespace for FW_ACTIVATE reload action")
> Signed-off-by: Or Har-Toov <ohartoov@nvidia.com>
> Reviewed-by: Jiri Pirko <jiri@nvidia.com>
> Signed-off-by: Tariq Toukan <tariqt@nvidia.com>

Reviewed-by: Antoine Tenart <atenart@kernel.org>

> ---
>  net/devlink/dev.c | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/net/devlink/dev.c b/net/devlink/dev.c
> index 57b2b8f03543..fd5633fa88ec 100644
> --- a/net/devlink/dev.c
> +++ b/net/devlink/dev.c
> @@ -578,6 +578,7 @@ int devlink_nl_reload_doit(struct sk_buff *skb, struct genl_info *info)
>  		    action != DEVLINK_RELOAD_ACTION_DRIVER_REINIT) {
>  			NL_SET_ERR_MSG_MOD(info->extack,
>  					   "Changing namespace is only supported for reinit action");
> +			put_net(dest_net);
>  			return -EOPNOTSUPP;
>  		}
>  	}
> 
> base-commit: 3bd438a58e910db5dc369aa25dfed1fc95f1b596
> -- 
> 2.44.0
> 

      reply	other threads:[~2026-07-29 10:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-29  8:06 [PATCH net] devlink: fix net namespace reference leak in reload Tariq Toukan
2026-07-29 10:23 ` Antoine Tenart [this message]

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=amnUeT6MHSNvnM_b@kwain \
    --to=atenart@kernel.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=gal@nvidia.com \
    --cc=horms@kernel.org \
    --cc=jiri@nvidia.com \
    --cc=jiri@resnulli.us \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=ohartoov@nvidia.com \
    --cc=pabeni@redhat.com \
    --cc=tariqt@nvidia.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