[EXT] Re: [PATCH v2] cryptodev: fix device socket ID type

Akhil Goyal gakhil at marvell.com
Wed Jul 5 20:23:40 CEST 2023


> 05/07/2023 11:36, Ciara Power пишет:
> > The socket ID field for a cryptodev device data was unsigned int.
> > Due to recent changes to the default device socket ID,
> > this caused an issue when the socket ID was unknown and set to -1.
> > The device socket ID wrapped around to 255,
> > and caused errors when allocating memory.
> >
> > Changing this field type to int fixes the issue, as it now takes the
> > correct -1 value.
> >
> > Fixes: 7dcd73e37965 ("drivers/bus: set device NUMA node to unknown by
> default")
> > Cc: olivier.matz at 6wind.com
> > Cc: stable at dpdk.org
> >
> > Signed-off-by: Ciara Power <ciara.power at intel.com>
> > Acked-by: Morten Brørup <mb at smartsharesystems.com>
> > Acked-by: Kai Ji <kai.ji at intel.com>
> >
> Acked-by: Konstantin Ananyev <konstantin.v.ananyev at yandex.ru>
Acked-by: Akhil Goyal <gakhil at marvell.com>
Applied to dpdk-next-crypto
Thanks.


More information about the stable mailing list