From: Akhil Goyal <gakhil@marvell.com>
To: Rebecca Troy <rebecca.troy@intel.com>,
Fan Zhang <roy.fan.zhang@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"kai.ji@intel.com" <kai.ji@intel.com>,
"stable@dpdk.org" <stable@dpdk.org>
Subject: RE: [EXT] [PATCH] crypto/qat: fix secure session check
Date: Fri, 1 Jul 2022 18:31:10 +0000 [thread overview]
Message-ID: <CO6PR18MB4484B58FDB699B83BC5FA3A0D8BD9@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <20220701085707.246099-1-rebecca.troy@intel.com>
> Currently when running the dpdk-perf-test with docsis
> security sessions, a segmentation fault occurs. This
> is due to the check being made that the session is not
> equal to op->sym->sec_session. This check passes the
> first time but on the second iteration fails and doesn't
> create the build_request.
>
> This commit fixes that error by getting the ctx first
> from the private session data and then comparing ctx,
> rather than op->sym->sec_session, with the sess.
>
> Fixes: fb3b9f492205 ("crypto/qat: rework burst data path")
> Cc: kai.ji@intel.com
> Cc: stable@dpdk.org
>
> Signed-off-by: Rebecca Troy <rebecca.troy@intel.com>
> ---
> drivers/crypto/qat/qat_sym.c | 10 +++++-----
> 1 file changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/crypto/qat/qat_sym.c b/drivers/crypto/qat/qat_sym.c
> index 3477cd89ad..e5ae670b3a 100644
> --- a/drivers/crypto/qat/qat_sym.c
> +++ b/drivers/crypto/qat/qat_sym.c
> @@ -105,16 +105,16 @@ qat_sym_build_request(void *in_op, uint8_t
> *out_msg,
>
> #ifdef RTE_LIB_SECURITY
> else if (op->sess_type == RTE_CRYPTO_OP_SECURITY_SESSION) {
> - if ((void *)sess != (void *)op->sym->sec_session) {
> - struct rte_cryptodev *cdev;
> - struct qat_cryptodev_private *internals;
> -
> - ctx = get_sec_session_private_data(
> + ctx = get_sec_session_private_data(
> op->sym->sec_session);
> if (unlikely(!ctx)) {
> QAT_DP_LOG(ERR, "No session for this
> device");
> return -EINVAL;
> }
Fix formatting of above if check.
> + if (sess != (uintptr_t)ctx) {
> + struct rte_cryptodev *cdev;
> + struct qat_cryptodev_private *internals;
> +
> if (unlikely(ctx->bpi_ctx == NULL)) {
> QAT_DP_LOG(ERR, "QAT PMD only supports
> security"
> " operation requests for"
> --
> 2.25.1
next prev parent reply other threads:[~2022-07-01 18:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-01 8:57 Rebecca Troy
2022-07-01 18:31 ` Akhil Goyal [this message]
2022-07-05 13:28 ` [dpdk-dev v2] " Kai Ji
2022-07-05 16:32 ` [EXT] " 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=CO6PR18MB4484B58FDB699B83BC5FA3A0D8BD9@CO6PR18MB4484.namprd18.prod.outlook.com \
--to=gakhil@marvell.com \
--cc=dev@dpdk.org \
--cc=kai.ji@intel.com \
--cc=rebecca.troy@intel.com \
--cc=roy.fan.zhang@intel.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).