From: Tariq Toukan <ttoukan.linux@gmail.com>
To: Charles Han <hanchunchao@inspur.com>
Cc: andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, leon@kernel.org, linux-kernel@vger.kernel.org,
linux-rdma@vger.kernel.org, markzhang@nvidia.com,
mbloch@nvidia.com, netdev@vger.kernel.org, pabeni@redhat.com,
przemyslaw.kitszel@intel.com, saeedm@nvidia.com,
tariqt@nvidia.com
Subject: Re: [PATCH V2] net/mlx5: fix potential null dereference when enable shared FDB
Date: Mon, 7 Apr 2025 12:28:24 +0300 [thread overview]
Message-ID: <73ec97a8-2ef8-468f-86fc-4de9e5e74b5e@gmail.com> (raw)
In-Reply-To: <20250407064757.4266-1-hanchunchao@inspur.com>
On 07/04/2025 9:47, Charles Han wrote:
> mlx5_get_flow_namespace() may return a NULL pointer, dereferencing it
> without NULL check may lead to NULL dereference.
> Add a NULL check for ns.
>
> Fixes: db202995f503 ("net/mlx5: E-Switch, add logic to enable shared FDB")
> Signed-off-by: Charles Han <hanchunchao@inspur.com>
> ---
> .../net/ethernet/mellanox/mlx5/core/eswitch_offloads.c | 10 ++++++++++
> drivers/net/ethernet/mellanox/mlx5/core/fs_cmd.c | 5 +++++
> 2 files changed, 15 insertions(+)
>
> diff --git a/drivers/net/ethernet/mellanox/mlx5/core/eswitch_offloads.c b/drivers/net/ethernet/mellanox/mlx5/core/eswitch_offloads.c
> index a6a8eea5980c..5405134e74b6 100644
> --- a/drivers/net/ethernet/mellanox/mlx5/core/eswitch_offloads.c
> +++ b/drivers/net/ethernet/mellanox/mlx5/core/eswitch_offloads.c
> @@ -2667,6 +2667,11 @@ static int esw_set_slave_root_fdb(struct mlx5_core_dev *master,
> if (master) {
> ns = mlx5_get_flow_namespace(master,
> MLX5_FLOW_NAMESPACE_FDB);
> + if (!ns) {
> + esw_warn(master, "Failed to get flow namespace\n");
> + return -EOPNOTSUPP;
> + }
> +
> root = find_root(&ns->node);
> mutex_lock(&root->chain_lock);
> MLX5_SET(set_flow_table_root_in, in,
> @@ -2679,6 +2684,11 @@ static int esw_set_slave_root_fdb(struct mlx5_core_dev *master,
> } else {
> ns = mlx5_get_flow_namespace(slave,
> MLX5_FLOW_NAMESPACE_FDB);
> + if (!ns) {
> + esw_warn(slave, "Failed to get flow namespace\n");
> + return -EOPNOTSUPP;
> + }
> +
> root = find_root(&ns->node);
> mutex_lock(&root->chain_lock);
> MLX5_SET(set_flow_table_root_in, in, table_id,
> diff --git a/drivers/net/ethernet/mellanox/mlx5/core/fs_cmd.c b/drivers/net/ethernet/mellanox/mlx5/core/fs_cmd.c
> index a47c29571f64..18e59f6a0f2d 100644
> --- a/drivers/net/ethernet/mellanox/mlx5/core/fs_cmd.c
> +++ b/drivers/net/ethernet/mellanox/mlx5/core/fs_cmd.c
> @@ -186,6 +186,11 @@ static int mlx5_cmd_set_slave_root_fdb(struct mlx5_core_dev *master,
> } else {
> ns = mlx5_get_flow_namespace(slave,
> MLX5_FLOW_NAMESPACE_FDB);
> + if (!ns) {
> + mlx5_core_warn(slave, "Failed to get flow namespace\n");
> + return -EOPNOTSUPP;
> + }
> +
> root = find_root(&ns->node);
> MLX5_SET(set_flow_table_root_in, in, table_id,
> root->root_ft->id);
Thanks for your patch.
I wonder, did you fail on any of these, or just caught them while
reading the code?
prev parent reply other threads:[~2025-04-07 9:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-03 9:52 [PATCH] " Charles Han(韩春超)
2025-04-03 14:03 ` Tariq Toukan
2025-04-03 18:32 ` Tariq Toukan
2025-04-07 6:47 ` [PATCH V2] " Charles Han
2025-04-07 9:28 ` Tariq Toukan [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=73ec97a8-2ef8-468f-86fc-4de9e5e74b5e@gmail.com \
--to=ttoukan.linux@gmail.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hanchunchao@inspur.com \
--cc=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=markzhang@nvidia.com \
--cc=mbloch@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=przemyslaw.kitszel@intel.com \
--cc=saeedm@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
all inboxes | Powered by JetHome®