From: Eric Dumazet <eric.dumazet@gmail.com>
To: Aditya Pakki <pakki001@umn.edu>
Cc: kjlu@umn.edu, Boris Pismenny <borisp@mellanox.com>,
Saeed Mahameed <saeedm@mellanox.com>,
Leon Romanovsky <leon@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Ilya Lesokhin <ilyal@mellanox.com>,
Wei Yongjun <weiyongjun1@huawei.com>,
netdev@vger.kernel.org, linux-rdma@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4] net: mlx5: Add a missing check on idr_find, free buf
Date: Tue, 19 Mar 2019 21:54:10 -0700 [thread overview]
Message-ID: <d65ddd7e-6553-00a4-c261-bd88b7476626@gmail.com> (raw)
In-Reply-To: <20190319214244.20212-1-pakki001@umn.edu>
On 03/19/2019 02:42 PM, Aditya Pakki wrote:
> idr_find() can return a NULL value to 'flow' which is used without a
> check. The patch adds a check to avoid potential NULL pointer dereference.
>
> In case of mlx5_fpga_sbu_conn_sendmsg() failure, free buf allocated
> using kzalloc.
>
> Fixes: ab412e1dd7db ("net/mlx5: Accel, add TLS rx offload routines")
> ---
> v3: Reorder buf allocations and flow check.
> v2: failure to return in case of flow failure.
> v1: Failed to free buf in case of flow failure.
>
> Signed-off-by: Aditya Pakki <pakki001@umn.edu>
> ---
> drivers/net/ethernet/mellanox/mlx5/core/fpga/tls.c | 14 +++++++++++---
> 1 file changed, 11 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/net/ethernet/mellanox/mlx5/core/fpga/tls.c b/drivers/net/ethernet/mellanox/mlx5/core/fpga/tls.c
> index 5cf5f2a9d51f..8de64e88c670 100644
> --- a/drivers/net/ethernet/mellanox/mlx5/core/fpga/tls.c
> +++ b/drivers/net/ethernet/mellanox/mlx5/core/fpga/tls.c
> @@ -217,15 +217,21 @@ int mlx5_fpga_tls_resync_rx(struct mlx5_core_dev *mdev, u32 handle, u32 seq,
> void *cmd;
> int ret;
>
> + rcu_read_lock();
> + flow = idr_find(&mdev->fpga->tls->rx_idr, ntohl(handle));
> + rcu_read_unlock();
This looks suspect (even before your patch)
What prevents flow from disappearing after this rcu_read_lock() ?
IMO your patch might prevent a NULL deref, but not use-after-free.
> +
> + if (!flow) {
> + WARN_ONCE(1, "Received NULL pointer for handle\n");
> + return -EINVAL;
> + }
> +
> buf = kzalloc(size, GFP_ATOMIC);
> if (!buf)
> return -ENOMEM;
>
> cmd = (buf + 1);
>
> - rcu_read_lock();
> - flow = idr_find(&mdev->fpga->tls->rx_idr, ntohl(handle));
> - rcu_read_unlock();
> mlx5_fpga_tls_flow_to_cmd(flow, cmd);
>
> MLX5_SET(tls_cmd, cmd, swid, ntohl(handle));
> @@ -238,6 +244,8 @@ int mlx5_fpga_tls_resync_rx(struct mlx5_core_dev *mdev, u32 handle, u32 seq,
> buf->complete = mlx_tls_kfree_complete;
>
> ret = mlx5_fpga_sbu_conn_sendmsg(mdev->fpga->tls->conn, buf);
> + if (ret < 0)
> + kfree(buf);
>
> return ret;
> }
>
next prev parent reply other threads:[~2019-03-20 4:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-19 21:42 [PATCH v4] net: mlx5: Add a missing check on idr_find, free buf Aditya Pakki
2019-03-19 22:37 ` Saeed Mahameed
2019-03-20 4:54 ` Eric Dumazet [this message]
2019-03-20 5:02 ` Saeed Mahameed
2019-03-20 9:49 ` Boris Pismenny
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=d65ddd7e-6553-00a4-c261-bd88b7476626@gmail.com \
--to=eric.dumazet@gmail.com \
--cc=borisp@mellanox.com \
--cc=davem@davemloft.net \
--cc=ilyal@mellanox.com \
--cc=kjlu@umn.edu \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pakki001@umn.edu \
--cc=saeedm@mellanox.com \
--cc=weiyongjun1@huawei.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