DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Kusztal, ArkadiuszX" <arkadiuszx.kusztal@intel.com>
To: Akhil Goyal <gakhil@marvell.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "Dooley, Brian" <brian.dooley@intel.com>,
	"stable@dpdk.org" <stable@dpdk.org>
Subject: RE: [EXTERNAL] [PATCH v2] crypto/qat: fix ecdsa session handling
Date: Wed, 6 Nov 2024 14:44:39 +0000	[thread overview]
Message-ID: <CO1PR11MB5009F71544BC8FDDF79245E39F532@CO1PR11MB5009.namprd11.prod.outlook.com> (raw)
In-Reply-To: <CO6PR18MB4484C1BB67D75E94F117A1E6D8532@CO6PR18MB4484.namprd18.prod.outlook.com>



> -----Original Message-----
> From: Akhil Goyal <gakhil@marvell.com>
> Sent: Wednesday, November 6, 2024 12:52 PM
> To: Kusztal, ArkadiuszX <arkadiuszx.kusztal@intel.com>; dev@dpdk.org
> Cc: Dooley, Brian <brian.dooley@intel.com>; stable@dpdk.org
> Subject: RE: [EXTERNAL] [PATCH v2] crypto/qat: fix ecdsa session handling
> 
> > Fixed a problem with setting the key in the session in the ECDSA
> > alghorithm.
> 
> Please elaborate what is the problem and what is being done in the patch.
> 
> >
> > Fixes: badc0c6f6d6a ("cryptodev: set private and public keys in EC
> > session")
> > Cc: stable@dpdk.org
> >
> > Signed-off-by: Arkadiusz Kusztal <arkadiuszx.kusztal@intel.com>
> > ---
> >  drivers/crypto/qat/qat_asym.c | 41
> > +++++++++++++++++++++++++++++++++--
> >  1 file changed, 39 insertions(+), 2 deletions(-)
> >
> > diff --git a/drivers/crypto/qat/qat_asym.c
> > b/drivers/crypto/qat/qat_asym.c index 9e97582e22..dfc52d1286 100644
> > --- a/drivers/crypto/qat/qat_asym.c
> > +++ b/drivers/crypto/qat/qat_asym.c
> > @@ -1346,11 +1346,48 @@ session_set_rsa(struct qat_asym_session
> > *qat_session,
> >  	return ret;
> >  }
> >
> > -static void
> > +static int
> >  session_set_ec(struct qat_asym_session *qat_session,
> >  			struct rte_crypto_asym_xform *xform)  {
> > +	uint8_t *pkey = xform->ec.pkey.data;
> > +	uint8_t *q_x = xform->ec.q.x.data;
> > +	uint8_t *q_y = xform->ec.q.y.data;
> > +
> > +	qat_session->xform.ec.pkey.data =
> > +		rte_malloc(NULL, xform->ec.pkey.length, 0);
> > +	if (qat_session->xform.ec.pkey.length &&
> > +		qat_session->xform.ec.pkey.data == NULL)
> > +		return -ENOMEM;
> > +	qat_session->xform.ec.q.x.data = rte_malloc(NULL,
> > +		xform->ec.q.x.length, 0);
> > +	if (qat_session->xform.ec.q.x.length &&
> > +		qat_session->xform.ec.q.x.data == NULL) {
> > +		rte_free(qat_session->xform.ec.pkey.data);
> > +		return -ENOMEM;
> > +	}
> > +	qat_session->xform.ec.q.y.data = rte_malloc(NULL,
> > +		xform->ec.q.y.length, 0);
> > +	if (qat_session->xform.ec.q.y.length &&
> > +		qat_session->xform.ec.q.y.data == NULL) {
> > +		rte_free(qat_session->xform.ec.pkey.data);
> > +		rte_free(qat_session->xform.ec.q.x.data);
> > +		return -ENOMEM;
> > +	}
> > +
> > +	rte_memcpy(qat_session->xform.ec.pkey.data, pkey,
> > +		xform->ec.pkey.length);
> > +	qat_session->xform.ec.pkey.length = xform->ec.pkey.length;
> > +	rte_memcpy(qat_session->xform.ec.q.x.data, q_x,
> > +		xform->ec.q.x.length);
> > +	qat_session->xform.ec.q.x.length = xform->ec.q.x.length;
> > +	rte_memcpy(qat_session->xform.ec.q.y.data, q_y,
> > +		xform->ec.q.y.length);
> 
> Do you really need rte_memcpy?
> memcpy is not enough?

This is a session, so yes, this can be a memcpy call.
I will change.

> 
> > +	qat_session->xform.ec.q.y.length = xform->ec.q.y.length;
> >  	qat_session->xform.ec.curve_id = xform->ec.curve_id;
> > +
> > +	return 0;
> > +
> >  }
> >
> >  int
> > @@ -1386,7 +1423,7 @@ qat_asym_session_configure(struct rte_cryptodev
> > *dev __rte_unused,
> >  	case RTE_CRYPTO_ASYM_XFORM_ECDSA:
> >  	case RTE_CRYPTO_ASYM_XFORM_ECPM:
> >  	case RTE_CRYPTO_ASYM_XFORM_ECDH:
> > -		session_set_ec(qat_session, xform);
> > +		ret = session_set_ec(qat_session, xform);
> >  		break;
> >  	case RTE_CRYPTO_ASYM_XFORM_SM2:
> >  		break;
> > --
> > 2.34.1


  reply	other threads:[~2024-11-06 14:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-31 19:19 [PATCH] " Arkadiusz Kusztal
2024-11-04  9:30 ` [PATCH v2] " Arkadiusz Kusztal
2024-11-06 11:51   ` [EXTERNAL] " Akhil Goyal
2024-11-06 14:44     ` Kusztal, ArkadiuszX [this message]
2024-11-06 15:14   ` [PATCH v3] " Arkadiusz Kusztal
2024-11-06 17:44     ` [EXTERNAL] " Akhil Goyal

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CO1PR11MB5009F71544BC8FDDF79245E39F532@CO1PR11MB5009.namprd11.prod.outlook.com \
    --to=arkadiuszx.kusztal@intel.com \
    --cc=brian.dooley@intel.com \
    --cc=dev@dpdk.org \
    --cc=gakhil@marvell.com \
    --cc=stable@dpdk.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).