RE: [PATCH] crypto: fix asymmetric private session variable size

2022-02-22 Thread Akhil Goyal
> > > When creating the asymmetric session mempool, the maximum private > > > session size of all devices is used when creating the mempool object > > > size. > > > The return value for ``rte_cryptodev_asym_get_private_session_size`` > > > is unsigned int, whereas the variable was uint8_t, leading

RE: [PATCH] crypto: fix asymmetric private session variable size

2022-02-21 Thread Kusztal, ArkadiuszX
> -Original Message- > From: Zhang, Roy Fan > Sent: Friday, February 18, 2022 3:08 PM > To: Power, Ciara ; dev@dpdk.org > Cc: gak...@marvell.com; Kusztal, ArkadiuszX > Subject: RE: [PATCH] crypto: fix asymmetric private session variable size > > > -Ori

RE: [PATCH] crypto: fix asymmetric private session variable size

2022-02-18 Thread Zhang, Roy Fan
> -Original Message- > From: Power, Ciara > Sent: Friday, February 18, 2022 12:58 PM > To: dev@dpdk.org > Cc: Zhang, Roy Fan ; gak...@marvell.com; Kusztal, > ArkadiuszX ; Power, Ciara > > Subject: [PATCH] crypto: fix asymmetric private session variable siz

RE: [PATCH] crypto: fix asymmetric private session variable size

2022-02-18 Thread Zhang, Roy Fan
Hi Ciara, > -Original Message- > From: Power, Ciara > Sent: Friday, February 18, 2022 12:58 PM > To: dev@dpdk.org > Cc: Zhang, Roy Fan ; gak...@marvell.com; Kusztal, > ArkadiuszX ; Power, Ciara > > Subject: [PATCH] crypto: fix asymmetric private session variable

[PATCH] crypto: fix asymmetric private session variable size

2022-02-18 Thread Ciara Power
When creating the asymmetric session mempool, the maximum private session size of all devices is used when creating the mempool object size. The return value for ``rte_cryptodev_asym_get_private_session_size`` is unsigned int, whereas the variable was uint8_t, leading to a possible overflow issue.