[PATCH 1/2] mempool: make event callbacks process-private

Dmitry Kozlyuk dkozlyuk at nvidia.com
Thu Sep 22 09:31:09 CEST 2022


> From: Dmitry Kozlyuk <dkozlyuk at nvidia.com>
> Sent: Monday, August 8, 2022 12:43 PM
> To: dev at dpdk.org
> Cc: Olivier Matz <olivier.matz at 6wind.com>; Andrew Rybchenko
> <andrew.rybchenko at oktetlabs.ru>; stable at dpdk.org
> Subject: [PATCH 1/2] mempool: make event callbacks process-private
> 
> Callbacks for mempool events were registered in a process-shared tailq.
> This was inherently incorrect because the same function
> may be loaded to a different address in each process.
> Make the tailq process-private.
> Use the EAL tailq lock to reduce the number of different locks
> this module operates.
> 
> Fixes: da2b9cb25e5f ("mempool: add event callbacks")
> Cc: stable at dpdk.org
> 
> Signed-off-by: Dmitry Kozlyuk <dkozlyuk at nvidia.com>

Kind reminder to the mempool maintainers.


More information about the stable mailing list