* [dpdk-stable] [dpdk-dev] [PATCH v2 1/2] net/mlx4: fix mem leak when a device configured repeatedly
[not found] <cover.1620876356.git.wangyunjian@huawei.com>
@ 2021-05-13 3:38 ` wangyunjian
2021-05-13 6:46 ` Slava Ovsiienko
2021-05-13 3:39 ` [dpdk-stable] [dpdk-dev] [PATCH v2 2/2] net/mlx5: " wangyunjian
1 sibling, 1 reply; 4+ messages in thread
From: wangyunjian @ 2021-05-13 3:38 UTC (permalink / raw)
To: dev; +Cc: matan, shahafs, viacheslavo, dingxiaoxiong, Yunjian Wang, stable
From: Yunjian Wang <wangyunjian@huawei.com>
Currently, configuring a mlx device, it will allocate its
own process private in mlx5_proc_priv_init() and only frees
it when closing the device. This will lead to a memory leak,
when a device is configured repeatedly.
For example:
for(...)
do
rte_eth_dev_configure
rte_eth_rx_queue_setup
rte_eth_tx_queue_setup
rte_eth_dev_start
rte_eth_dev_stop
done
Fixes: 97d37d2c1f6b ("net/mlx4: remove device register remap")
Cc: stable@dpdk.org
Signed-off-by: Yunjian Wang <wangyunjian@huawei.com>
---
drivers/net/mlx4/mlx4.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/net/mlx4/mlx4.c b/drivers/net/mlx4/mlx4.c
index 7cd35cd3ca..c522157a0a 100644
--- a/drivers/net/mlx4/mlx4.c
+++ b/drivers/net/mlx4/mlx4.c
@@ -201,6 +201,7 @@ mlx4_proc_priv_init(struct rte_eth_dev *dev)
struct mlx4_proc_priv *ppriv;
size_t ppriv_size;
+ mlx4_proc_priv_uninit(dev);
/*
* UAR register table follows the process private structure. BlueFlame
* registers for Tx queues are stored in the table.
--
2.23.0
^ permalink raw reply [flat|nested] 4+ messages in thread* Re: [dpdk-stable] [dpdk-dev] [PATCH v2 1/2] net/mlx4: fix mem leak when a device configured repeatedly
2021-05-13 3:38 ` [dpdk-stable] [dpdk-dev] [PATCH v2 1/2] net/mlx4: fix mem leak when a device configured repeatedly wangyunjian
@ 2021-05-13 6:46 ` Slava Ovsiienko
0 siblings, 0 replies; 4+ messages in thread
From: Slava Ovsiienko @ 2021-05-13 6:46 UTC (permalink / raw)
To: wangyunjian, dev; +Cc: Matan Azrad, Shahaf Shuler, dingxiaoxiong, stable
> -----Original Message-----
> From: wangyunjian <wangyunjian@huawei.com>
> Sent: Thursday, May 13, 2021 6:39
> To: dev@dpdk.org
> Cc: Matan Azrad <matan@nvidia.com>; Shahaf Shuler
> <shahafs@nvidia.com>; Slava Ovsiienko <viacheslavo@nvidia.com>;
> dingxiaoxiong@huawei.com; Yunjian Wang <wangyunjian@huawei.com>;
> stable@dpdk.org
> Subject: [dpdk-dev] [PATCH v2 1/2] net/mlx4: fix mem leak when a device
> configured repeatedly
>
> From: Yunjian Wang <wangyunjian@huawei.com>
>
> Currently, configuring a mlx device, it will allocate its own process private in
> mlx5_proc_priv_init() and only frees it when closing the device. This will lead
> to a memory leak, when a device is configured repeatedly.
>
> For example:
> for(...)
> do
> rte_eth_dev_configure
> rte_eth_rx_queue_setup
> rte_eth_tx_queue_setup
> rte_eth_dev_start
> rte_eth_dev_stop
> done
>
> Fixes: 97d37d2c1f6b ("net/mlx4: remove device register remap")
> Cc: stable@dpdk.org
>
> Signed-off-by: Yunjian Wang <wangyunjian@huawei.com>
Acked-by: Viacheslav Ovsiienko <viacheslavo@nvidia.com>
^ permalink raw reply [flat|nested] 4+ messages in thread
* [dpdk-stable] [dpdk-dev] [PATCH v2 2/2] net/mlx5: fix mem leak when a device configured repeatedly
[not found] <cover.1620876356.git.wangyunjian@huawei.com>
2021-05-13 3:38 ` [dpdk-stable] [dpdk-dev] [PATCH v2 1/2] net/mlx4: fix mem leak when a device configured repeatedly wangyunjian
@ 2021-05-13 3:39 ` wangyunjian
2021-05-13 6:47 ` Slava Ovsiienko
1 sibling, 1 reply; 4+ messages in thread
From: wangyunjian @ 2021-05-13 3:39 UTC (permalink / raw)
To: dev; +Cc: matan, shahafs, viacheslavo, dingxiaoxiong, Yunjian Wang, stable
From: Yunjian Wang <wangyunjian@huawei.com>
Currently, configuring a mlx device, it will allocate its
own process private in mlx5_proc_priv_init() and only frees
it when closing the device. This will lead to a memory leak,
when a device is configured repeatedly.
For example:
for(...)
do
rte_eth_dev_configure
rte_eth_rx_queue_setup
rte_eth_tx_queue_setup
rte_eth_dev_start
rte_eth_dev_stop
done
Fixes: 120dc4a7dcd3 ("net/mlx5: remove device register remap")
Cc: stable@dpdk.org
Signed-off-by: Yunjian Wang <wangyunjian@huawei.com>
---
drivers/net/mlx5/mlx5.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/net/mlx5/mlx5.c b/drivers/net/mlx5/mlx5.c
index 35f91e965e..cf1815cb74 100644
--- a/drivers/net/mlx5/mlx5.c
+++ b/drivers/net/mlx5/mlx5.c
@@ -1455,6 +1455,7 @@ mlx5_proc_priv_init(struct rte_eth_dev *dev)
struct mlx5_proc_priv *ppriv;
size_t ppriv_size;
+ mlx5_proc_priv_uninit(dev);
/*
* UAR register table follows the process private structure. BlueFlame
* registers for Tx queues are stored in the table.
--
2.23.0
^ permalink raw reply [flat|nested] 4+ messages in thread* Re: [dpdk-stable] [dpdk-dev] [PATCH v2 2/2] net/mlx5: fix mem leak when a device configured repeatedly
2021-05-13 3:39 ` [dpdk-stable] [dpdk-dev] [PATCH v2 2/2] net/mlx5: " wangyunjian
@ 2021-05-13 6:47 ` Slava Ovsiienko
0 siblings, 0 replies; 4+ messages in thread
From: Slava Ovsiienko @ 2021-05-13 6:47 UTC (permalink / raw)
To: wangyunjian, dev; +Cc: Matan Azrad, Shahaf Shuler, dingxiaoxiong, stable
> -----Original Message-----
> From: wangyunjian <wangyunjian@huawei.com>
> Sent: Thursday, May 13, 2021 6:40
> To: dev@dpdk.org
> Cc: Matan Azrad <matan@nvidia.com>; Shahaf Shuler
> <shahafs@nvidia.com>; Slava Ovsiienko <viacheslavo@nvidia.com>;
> dingxiaoxiong@huawei.com; Yunjian Wang <wangyunjian@huawei.com>;
> stable@dpdk.org
> Subject: [dpdk-dev] [PATCH v2 2/2] net/mlx5: fix mem leak when a device
> configured repeatedly
>
> From: Yunjian Wang <wangyunjian@huawei.com>
>
> Currently, configuring a mlx device, it will allocate its own process private in
> mlx5_proc_priv_init() and only frees it when closing the device. This will lead
> to a memory leak, when a device is configured repeatedly.
>
> For example:
> for(...)
> do
> rte_eth_dev_configure
> rte_eth_rx_queue_setup
> rte_eth_tx_queue_setup
> rte_eth_dev_start
> rte_eth_dev_stop
> done
>
> Fixes: 120dc4a7dcd3 ("net/mlx5: remove device register remap")
> Cc: stable@dpdk.org
>
> Signed-off-by: Yunjian Wang <wangyunjian@huawei.com>
Acked-by: Viacheslav Ovsiienko <viacheslavo@nvidia.com>
^ permalink raw reply [flat|nested] 4+ messages in thread