* [PATCH] crypto: fix asymmetric private session variable size
@ 2022-02-18 12:57 Ciara Power
2022-02-18 13:39 ` Zhang, Roy Fan
2022-02-18 14:08 ` Zhang, Roy Fan
0 siblings, 2 replies; 5+ messages in thread
From: Ciara Power @ 2022-02-18 12:57 UTC (permalink / raw)
To: dev; +Cc: roy.fan.zhang, gakhil, arkadiuszx.kusztal, 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.
To fix this, the variable for private session size is now changed to
unsigned int to match the function return type.
Fixes: 1f1e4b7cbaad ("cryptodev: use single mempool for asymmetric session")
Reported-by: Arek Kusztal <arkadiuszx.kusztal@intel.com>
Signed-off-by: Ciara Power <ciara.power@intel.com>
---
lib/cryptodev/rte_cryptodev.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/lib/cryptodev/rte_cryptodev.c b/lib/cryptodev/rte_cryptodev.c
index 727d271fb9..d262ae6ffa 100644
--- a/lib/cryptodev/rte_cryptodev.c
+++ b/lib/cryptodev/rte_cryptodev.c
@@ -1810,7 +1810,8 @@ rte_cryptodev_asym_session_pool_create(const char *name, uint32_t nb_elts,
struct rte_mempool *mp;
struct rte_cryptodev_asym_session_pool_private_data *pool_priv;
uint32_t obj_sz, obj_sz_aligned;
- uint8_t dev_id, priv_sz, max_priv_sz = 0;
+ uint8_t dev_id;
+ unsigned int priv_sz, max_priv_sz = 0;
for (dev_id = 0; dev_id < RTE_CRYPTO_MAX_DEVS; dev_id++)
if (rte_cryptodev_is_valid_dev(dev_id)) {
--
2.25.1
^ permalink raw reply [flat|nested] 5+ messages in thread
* RE: [PATCH] crypto: fix asymmetric private session variable size
2022-02-18 12:57 [PATCH] crypto: fix asymmetric private session variable size Ciara Power
@ 2022-02-18 13:39 ` Zhang, Roy Fan
2022-02-18 14:08 ` Zhang, Roy Fan
1 sibling, 0 replies; 5+ messages in thread
From: Zhang, Roy Fan @ 2022-02-18 13:39 UTC (permalink / raw)
To: Power, Ciara, dev; +Cc: gakhil, Kusztal, ArkadiuszX
Hi Ciara,
> -----Original Message-----
> From: Power, Ciara <ciara.power@intel.com>
> Sent: Friday, February 18, 2022 12:58 PM
> To: dev@dpdk.org
> Cc: Zhang, Roy Fan <roy.fan.zhang@intel.com>; gakhil@marvell.com; Kusztal,
> ArkadiuszX <arkadiuszx.kusztal@intel.com>; Power, Ciara
> <ciara.power@intel.com>
> Subject: [PATCH] crypto: fix asymmetric private session variable size
>
> 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.
>
> To fix this, the variable for private session size is now changed to
> unsigned int to match the function return type.
>
> Fixes: 1f1e4b7cbaad ("cryptodev: use single mempool for asymmetric
> session")
> Reported-by: Arek Kusztal <arkadiuszx.kusztal@intel.com>
>
> Signed-off-by: Ciara Power <ciara.power@intel.com>
> ---
> lib/cryptodev/rte_cryptodev.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/lib/cryptodev/rte_cryptodev.c b/lib/cryptodev/rte_cryptodev.c
> index 727d271fb9..d262ae6ffa 100644
> --- a/lib/cryptodev/rte_cryptodev.c
> +++ b/lib/cryptodev/rte_cryptodev.c
> @@ -1810,7 +1810,8 @@ rte_cryptodev_asym_session_pool_create(const
> char *name, uint32_t nb_elts,
> struct rte_mempool *mp;
> struct rte_cryptodev_asym_session_pool_private_data *pool_priv;
> uint32_t obj_sz, obj_sz_aligned;
> - uint8_t dev_id, priv_sz, max_priv_sz = 0;
> + uint8_t dev_id;
> + unsigned int priv_sz, max_priv_sz = 0;
I guess it is better to use uint32_t instead of unsigned int? I know they are most likely the same thing but probably better to use consistent type.
>
> for (dev_id = 0; dev_id < RTE_CRYPTO_MAX_DEVS; dev_id++)
> if (rte_cryptodev_is_valid_dev(dev_id)) {
> --
> 2.25.1
Regards,
Fan
^ permalink raw reply [flat|nested] 5+ messages in thread
* RE: [PATCH] crypto: fix asymmetric private session variable size
2022-02-18 12:57 [PATCH] crypto: fix asymmetric private session variable size Ciara Power
2022-02-18 13:39 ` Zhang, Roy Fan
@ 2022-02-18 14:08 ` Zhang, Roy Fan
2022-02-21 10:38 ` Kusztal, ArkadiuszX
1 sibling, 1 reply; 5+ messages in thread
From: Zhang, Roy Fan @ 2022-02-18 14:08 UTC (permalink / raw)
To: Power, Ciara, dev; +Cc: gakhil, Kusztal, ArkadiuszX
> -----Original Message-----
> From: Power, Ciara <ciara.power@intel.com>
> Sent: Friday, February 18, 2022 12:58 PM
> To: dev@dpdk.org
> Cc: Zhang, Roy Fan <roy.fan.zhang@intel.com>; gakhil@marvell.com; Kusztal,
> ArkadiuszX <arkadiuszx.kusztal@intel.com>; Power, Ciara
> <ciara.power@intel.com>
> Subject: [PATCH] crypto: fix asymmetric private session variable size
>
> 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.
>
> To fix this, the variable for private session size is now changed to
> unsigned int to match the function return type.
>
> Fixes: 1f1e4b7cbaad ("cryptodev: use single mempool for asymmetric
> session")
> Reported-by: Arek Kusztal <arkadiuszx.kusztal@intel.com>
>
> Signed-off-by: Ciara Power <ciara.power@intel.com>
> ---
> lib/cryptodev/rte_cryptodev.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/lib/cryptodev/rte_cryptodev.c b/lib/cryptodev/rte_cryptodev.c
> index 727d271fb9..d262ae6ffa 100644
> --- a/lib/cryptodev/rte_cryptodev.c
> +++ b/lib/cryptodev/rte_cryptodev.c
> @@ -1810,7 +1810,8 @@ rte_cryptodev_asym_session_pool_create(const
> char *name, uint32_t nb_elts,
> struct rte_mempool *mp;
> struct rte_cryptodev_asym_session_pool_private_data *pool_priv;
> uint32_t obj_sz, obj_sz_aligned;
> - uint8_t dev_id, priv_sz, max_priv_sz = 0;
> + uint8_t dev_id;
> + unsigned int priv_sz, max_priv_sz = 0;
>
> for (dev_id = 0; dev_id < RTE_CRYPTO_MAX_DEVS; dev_id++)
> if (rte_cryptodev_is_valid_dev(dev_id)) {
> --
> 2.25.1
Looks like the variable type of unsigned int is match the return type. So
Acked-by: Fan Zhang <roy.fan.zhang@intel.com>
^ permalink raw reply [flat|nested] 5+ messages in thread
* RE: [PATCH] crypto: fix asymmetric private session variable size
2022-02-18 14:08 ` Zhang, Roy Fan
@ 2022-02-21 10:38 ` Kusztal, ArkadiuszX
2022-02-22 19:02 ` Akhil Goyal
0 siblings, 1 reply; 5+ messages in thread
From: Kusztal, ArkadiuszX @ 2022-02-21 10:38 UTC (permalink / raw)
To: Zhang, Roy Fan, Power, Ciara, dev; +Cc: gakhil
> -----Original Message-----
> From: Zhang, Roy Fan <roy.fan.zhang@intel.com>
> Sent: Friday, February 18, 2022 3:08 PM
> To: Power, Ciara <ciara.power@intel.com>; dev@dpdk.org
> Cc: gakhil@marvell.com; Kusztal, ArkadiuszX <arkadiuszx.kusztal@intel.com>
> Subject: RE: [PATCH] crypto: fix asymmetric private session variable size
>
> > -----Original Message-----
> > From: Power, Ciara <ciara.power@intel.com>
> > Sent: Friday, February 18, 2022 12:58 PM
> > To: dev@dpdk.org
> > Cc: Zhang, Roy Fan <roy.fan.zhang@intel.com>; gakhil@marvell.com;
> > Kusztal, ArkadiuszX <arkadiuszx.kusztal@intel.com>; Power, Ciara
> > <ciara.power@intel.com>
> > Subject: [PATCH] crypto: fix asymmetric private session variable size
> >
> > 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.
> >
> > To fix this, the variable for private session size is now changed to
> > unsigned int to match the function return type.
> >
> > Fixes: 1f1e4b7cbaad ("cryptodev: use single mempool for asymmetric
> > session")
> > Reported-by: Arek Kusztal <arkadiuszx.kusztal@intel.com>
> >
> > Signed-off-by: Ciara Power <ciara.power@intel.com>
> > ---
> > lib/cryptodev/rte_cryptodev.c | 3 ++-
> > 1 file changed, 2 insertions(+), 1 deletion(-)
> >
> > diff --git a/lib/cryptodev/rte_cryptodev.c
> > b/lib/cryptodev/rte_cryptodev.c index 727d271fb9..d262ae6ffa 100644
> > --- a/lib/cryptodev/rte_cryptodev.c
> > +++ b/lib/cryptodev/rte_cryptodev.c
> > @@ -1810,7 +1810,8 @@ rte_cryptodev_asym_session_pool_create(const
> > char *name, uint32_t nb_elts,
> > struct rte_mempool *mp;
> > struct rte_cryptodev_asym_session_pool_private_data *pool_priv;
> > uint32_t obj_sz, obj_sz_aligned;
> > - uint8_t dev_id, priv_sz, max_priv_sz = 0;
> > + uint8_t dev_id;
> > + unsigned int priv_sz, max_priv_sz = 0;
> >
> > for (dev_id = 0; dev_id < RTE_CRYPTO_MAX_DEVS; dev_id++)
> > if (rte_cryptodev_is_valid_dev(dev_id)) {
> > --
> > 2.25.1
> Looks like the variable type of unsigned int is match the return type. So
> Acked-by: Fan Zhang <roy.fan.zhang@intel.com>
Acked-by: Arek Kusztal <arkadiuszx.kusztal@intel.com>
^ permalink raw reply [flat|nested] 5+ messages in thread
* RE: [PATCH] crypto: fix asymmetric private session variable size
2022-02-21 10:38 ` Kusztal, ArkadiuszX
@ 2022-02-22 19:02 ` Akhil Goyal
0 siblings, 0 replies; 5+ messages in thread
From: Akhil Goyal @ 2022-02-22 19:02 UTC (permalink / raw)
To: Kusztal, ArkadiuszX, Zhang, Roy Fan, Power, Ciara, dev
> > > 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.
> > >
> > > To fix this, the variable for private session size is now changed to
> > > unsigned int to match the function return type.
> > >
> > > Fixes: 1f1e4b7cbaad ("cryptodev: use single mempool for asymmetric
> > > session")
> > > Reported-by: Arek Kusztal <arkadiuszx.kusztal@intel.com>
> > >
> > > Signed-off-by: Ciara Power <ciara.power@intel.com>
> > > ---
> > Acked-by: Fan Zhang <roy.fan.zhang@intel.com>
> Acked-by: Arek Kusztal <arkadiuszx.kusztal@intel.com>
Applied to dpdk-next-crypto
Thanks.
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2022-02-22 19:02 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-02-18 12:57 [PATCH] crypto: fix asymmetric private session variable size Ciara Power
2022-02-18 13:39 ` Zhang, Roy Fan
2022-02-18 14:08 ` Zhang, Roy Fan
2022-02-21 10:38 ` Kusztal, ArkadiuszX
2022-02-22 19:02 ` Akhil Goyal
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).