DPDK patches and discussions
 help / color / mirror / Atom feed
* [dpdk-dev] [PATCH] net/mlx5: fix RxQ resource cleanup
@ 2021-10-18 17:24 Dmitry Kozlyuk
  2021-10-20 19:35 ` Raslan Darawsheh
  0 siblings, 1 reply; 2+ messages in thread
From: Dmitry Kozlyuk @ 2021-10-18 17:24 UTC (permalink / raw)
  To: dev; +Cc: Michael Baum, stable, Matan Azrad, Viacheslav Ovsiienko

mlx5_rxq_start() allocates rxq_ctrl->obj and frees it on failure,
but did not set it to NULL. Later mlx5_rxq_release() could not recognize
this object is already freed and attempted to release its resources,
resulting in a crash:

    Configuring Port 0 (socket 0)
    mlx5_common: Failed to create RQ using DevX
    mlx5_common: Can't create DevX RQ object.
    mlx5_net: Port 0 Rx queue 0 RQ creation failure.
    Segmentation fault

Set rxq_ctrl->obj to NULL after it is freed to skip resource release.

Fixes: 1260a87b2889 ("net/mlx5: share Rx control code")
Cc: Michael Baum <michaelba@nvidia.com>
Cc: stable@dpdk.org

Signed-off-by: Dmitry Kozlyuk <dkozlyuk@nvidia.com>
Acked-by: Matan Azrad <matan@nvidia.com>
---
 drivers/net/mlx5/mlx5_trigger.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/drivers/net/mlx5/mlx5_trigger.c b/drivers/net/mlx5/mlx5_trigger.c
index 54173bfacb..0ecdd776fc 100644
--- a/drivers/net/mlx5/mlx5_trigger.c
+++ b/drivers/net/mlx5/mlx5_trigger.c
@@ -182,6 +182,7 @@ mlx5_rxq_start(struct rte_eth_dev *dev)
 		ret = priv->obj_ops.rxq_obj_new(dev, i);
 		if (ret) {
 			mlx5_free(rxq_ctrl->obj);
+			rxq_ctrl->obj = NULL;
 			goto error;
 		}
 		DRV_LOG(DEBUG, "Port %u rxq %u updated with %p.",
-- 
2.25.1


^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: [dpdk-dev] [PATCH] net/mlx5: fix RxQ resource cleanup
  2021-10-18 17:24 [dpdk-dev] [PATCH] net/mlx5: fix RxQ resource cleanup Dmitry Kozlyuk
@ 2021-10-20 19:35 ` Raslan Darawsheh
  0 siblings, 0 replies; 2+ messages in thread
From: Raslan Darawsheh @ 2021-10-20 19:35 UTC (permalink / raw)
  To: Dmitry Kozlyuk, dev
  Cc: Michael Baum, stable, Matan Azrad, Viacheslav Ovsiienko

Hi,
> -----Original Message-----
> From: dev <dev-bounces@dpdk.org> On Behalf Of Dmitry Kozlyuk
> Sent: Monday, October 18, 2021 8:25 PM
> To: dev@dpdk.org
> Cc: Michael Baum <michaelba@oss.nvidia.com>; stable@dpdk.org; Matan
> Azrad <matan@oss.nvidia.com>; Viacheslav Ovsiienko
> <viacheslavo@oss.nvidia.com>
> Subject: [dpdk-dev] [PATCH] net/mlx5: fix RxQ resource cleanup
> 
> mlx5_rxq_start() allocates rxq_ctrl->obj and frees it on failure, but did not
> set it to NULL. Later mlx5_rxq_release() could not recognize this object is
> already freed and attempted to release its resources, resulting in a crash:
> 
>     Configuring Port 0 (socket 0)
>     mlx5_common: Failed to create RQ using DevX
>     mlx5_common: Can't create DevX RQ object.
>     mlx5_net: Port 0 Rx queue 0 RQ creation failure.
>     Segmentation fault
> 
> Set rxq_ctrl->obj to NULL after it is freed to skip resource release.
> 
> Fixes: 1260a87b2889 ("net/mlx5: share Rx control code")
> Cc: Michael Baum <michaelba@nvidia.com>
> Cc: stable@dpdk.org
> 
> Signed-off-by: Dmitry Kozlyuk <dkozlyuk@nvidia.com>
> Acked-by: Matan Azrad <matan@nvidia.com>

Patch applied to next-net-mlx,

Kindest regards,
Raslan Darawsheh

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2021-10-20 19:35 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-10-18 17:24 [dpdk-dev] [PATCH] net/mlx5: fix RxQ resource cleanup Dmitry Kozlyuk
2021-10-20 19:35 ` Raslan Darawsheh

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).