From: Ido Schimmel <idosch@nvidia.com>
To: Wentao Liang <vulab@iscas.ac.cn>
Cc: petrm@nvidia.com, andrew+netdev@lunn.ch, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH] mlxsw: fix refcount leak in mlxsw_sp_port_lag_join()
Date: Thu, 11 Jun 2026 09:17:08 +0300 [thread overview]
Message-ID: <20260611061708.GA836457@shredder> (raw)
In-Reply-To: <20260609083709.209743-1-vulab@iscas.ac.cn>
Subject prefix should be "[PATCH net]". See:
https://docs.kernel.org/process/maintainer-netdev.html
On Tue, Jun 09, 2026 at 08:37:09AM +0000, Wentao Liang wrote:
> When mlxsw_sp_port_lag_index_get() fails, mlxsw_sp_port_lag_join()
> returns an error without releasing the lag reference obtained by
> the earlier mlxsw_sp_lag_get(). All other error paths in the
> function jump to the cleanup label that ends with
> mlxsw_sp_lag_put(), so this is a single missed release.
>
> Fix the leak by replacing the bare 'return err' with a goto to the
> existing error cleanup label, which will drop the reference safely.
>
> Cc: stable@vger.kernel.org
> Fixes: 0d65fc13042f ("mlxsw: spectrum: Implement LAG port join/leave")
> Signed-off-by: Wentao Liang <vulab@iscas.ac.cn>
For net:
Reviewed-by: Ido Schimmel <idosch@nvidia.com>
> ---
> drivers/net/ethernet/mellanox/mlxsw/spectrum.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/net/ethernet/mellanox/mlxsw/spectrum.c b/drivers/net/ethernet/mellanox/mlxsw/spectrum.c
> index 3a65420fa1ad..fed708c17332 100644
> --- a/drivers/net/ethernet/mellanox/mlxsw/spectrum.c
> +++ b/drivers/net/ethernet/mellanox/mlxsw/spectrum.c
> @@ -4360,7 +4360,7 @@ static int mlxsw_sp_port_lag_join(struct mlxsw_sp_port *mlxsw_sp_port,
> lag_id = lag->lag_id;
> err = mlxsw_sp_port_lag_index_get(mlxsw_sp, lag_id, &port_index);
> if (err)
> - return err;
> + goto err_lag_uppers_bridge_join;
Convention in this code is to create a separate label, but it's not
worth another version
>
> err = mlxsw_sp_lag_uppers_bridge_join(mlxsw_sp_port, lag_dev,
> extack);
> --
> 2.34.1
>
prev parent reply other threads:[~2026-06-11 6:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-09 8:37 [PATCH] mlxsw: fix refcount leak in mlxsw_sp_port_lag_join() Wentao Liang
2026-06-11 6:17 ` Ido Schimmel [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=20260611061708.GA836457@shredder \
--to=idosch@nvidia.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=petrm@nvidia.com \
--cc=stable@vger.kernel.org \
--cc=vulab@iscas.ac.cn \
/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