From: Larysa Zaremba <larysa.zaremba@intel.com>
To: Dan Carpenter <dan.carpenter@linaro.org>
Cc: Shay Drory <shayd@nvidia.com>, Saeed Mahameed <saeedm@nvidia.com>,
"Leon Romanovsky" <leon@kernel.org>,
Tariq Toukan <tariqt@nvidia.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
"Jakub Kicinski" <kuba@kernel.org>,
Paolo Abeni <pabeni@redhat.com>, Moshe Shemesh <moshe@nvidia.com>,
<netdev@vger.kernel.org>, <linux-rdma@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <kernel-janitors@vger.kernel.org>
Subject: Re: [PATCH net] net/mlx5: Fix error handling in mlx5_init_one_light()
Date: Fri, 10 May 2024 08:44:26 +0200 [thread overview]
Message-ID: <Zj3CShR731VUdEUA@lzaremba-mobl.ger.corp.intel.com> (raw)
In-Reply-To: <a2bb6a55-5415-4c15-bee9-9e63f4b6a339@moroto.mountain>
On Thu, May 09, 2024 at 02:00:18PM +0300, Dan Carpenter wrote:
> If mlx5_query_hca_caps_light() fails then calling devl_unregister() or
> devl_unlock() is a bug. It's not registered and it's not locked. That
> will trigger a stack trace in this case because devl_unregister() checks
> both those things at the start of the function.
>
> If mlx5_devlink_params_register() fails then this code will call
> devl_unregister() and devl_unlock() twice which will again lead to a
> stack trace or possibly something worse as well.
>
> Fixes: bf729988303a ("net/mlx5: Restore mistakenly dropped parts in register devlink flow")
> Fixes: c6e77aa9dd82 ("net/mlx5: Register devlink first under devlink lock")
Reviewed-by: Larysa Zaremba <larysa.zaremba@intel.com>
> Signed-off-by: Dan Carpenter <dan.carpenter@linaro.org>
> ---
> drivers/net/ethernet/mellanox/mlx5/core/main.c | 10 ++++------
> 1 file changed, 4 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/net/ethernet/mellanox/mlx5/core/main.c b/drivers/net/ethernet/mellanox/mlx5/core/main.c
> index 331ce47f51a1..105c98160327 100644
> --- a/drivers/net/ethernet/mellanox/mlx5/core/main.c
> +++ b/drivers/net/ethernet/mellanox/mlx5/core/main.c
> @@ -1690,7 +1690,7 @@ int mlx5_init_one_light(struct mlx5_core_dev *dev)
> err = mlx5_query_hca_caps_light(dev);
> if (err) {
> mlx5_core_warn(dev, "mlx5_query_hca_caps_light err=%d\n", err);
> - goto query_hca_caps_err;
> + goto err_function_disable;
> }
>
> devl_lock(devlink);
> @@ -1699,18 +1699,16 @@ int mlx5_init_one_light(struct mlx5_core_dev *dev)
> err = mlx5_devlink_params_register(priv_to_devlink(dev));
> if (err) {
> mlx5_core_warn(dev, "mlx5_devlink_param_reg err = %d\n", err);
> - goto params_reg_err;
> + goto err_unregister;
> }
>
> devl_unlock(devlink);
> return 0;
>
> -params_reg_err:
> - devl_unregister(devlink);
> - devl_unlock(devlink);
> -query_hca_caps_err:
> +err_unregister:
> devl_unregister(devlink);
> devl_unlock(devlink);
> +err_function_disable:
> mlx5_function_disable(dev, true);
> out:
> dev->state = MLX5_DEVICE_STATE_INTERNAL_ERROR;
> --
> 2.43.0
>
>
next prev parent reply other threads:[~2024-05-10 6:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-09 11:00 [PATCH net] net/mlx5: Fix error handling in mlx5_init_one_light() Dan Carpenter
2024-05-10 6:44 ` Larysa Zaremba [this message]
2024-05-11 14:23 ` Simon Horman
2024-05-12 8:20 ` Dan Carpenter
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=Zj3CShR731VUdEUA@lzaremba-mobl.ger.corp.intel.com \
--to=larysa.zaremba@intel.com \
--cc=dan.carpenter@linaro.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=moshe@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=saeedm@nvidia.com \
--cc=shayd@nvidia.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