Hi,
> -----Original Message-----
> From: Bing Zhao <bi...@nvidia.com>
> Sent: Tuesday, November 23, 2021 2:49 PM
> To: Slava Ovsiienko <viachesl...@nvidia.com>; Matan Azrad
> <ma...@nvidia.com>
> Cc: dev@dpdk.org; Raslan Darawsheh <rasl...@nvidia.com>; Dmitry Kozlyuk
> <dkozl...@nvidia.com>
> Subject: [PATCH] common/mlx5: fix shared MR ranges allocation
>
> Memory regions (MRs) were allocated in one chunk of memory with a mempool
> registration object. However, MRs can be reused among different mempool
> registrations.
>
> When the registration that allocated the MRs originally was destroyed, the
> dangling pointers to the MRs could be left in other registrations sharing
> these
> MRs.
>
> Splitting the memory allocation of registration structure and MRs in this
> commit
> solves this pointer reference issue.
>
> Fixes: 690b2a88c2f7 ("common/mlx5: add mempool registration facilities")
>
> Signed-off-by: Bing Zhao <bi...@nvidia.com>
> Acked-by: Viacheslav Ovsiienko <viachesl...@nvidia.com>
> Reviewed-by: Dmitry Kozlyuk <dkozl...@nvidia.com>
Patch applied to next-net-mlx,
Kindest regards,
Raslan Darawsheh
