On 10/20/2023 1:06 PM, David Marchand wrote:
> In the process of releasing ethdev port in the primary process,
> secondary processes are asked to stop referencing such a port.
> Doing so, those processes can't predict whether the primary process
> will later invalidate/free the shared memory. So they may live with a
> reference to an old shared memory memzone and location in memory.
>
> Refresh the shared memory pointer in secondary process when requesting
> access to the shared memory: this is the best moment ethdev can check
> it because the primary process will (re-)create a shared memory only if
> no secondary process is referencing a ethdev port.
>
> Bugzilla ID: 1303
> Fixes: 36c46e738120 ("ethdev: cleanup shared data with the last port")
>
> Signed-off-by: David Marchand <david.march...@redhat.com>
>
Reviewed-by: Ferruh Yigit <ferruh.yi...@amd.com>
Applied to dpdk-next-net/main, thanks.
