From: "Power, Ciara" <ciara.power@intel.com>
To: "Kusztal, ArkadiuszX" <arkadiuszx.kusztal@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "gakhil@marvell.com" <gakhil@marvell.com>,
"stable@dpdk.org" <stable@dpdk.org>
Subject: RE: [PATCH] crypto/qat: fix ccm null aad pointer segfault
Date: Mon, 11 Mar 2024 14:35:18 +0000 [thread overview]
Message-ID: <SN7PR11MB7639EBE1D9C4EF43E65DB631E6242@SN7PR11MB7639.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20240308082512.5226-1-arkadiuszx.kusztal@intel.com>
> -----Original Message-----
> From: Kusztal, ArkadiuszX <arkadiuszx.kusztal@intel.com>
> Sent: Friday, March 8, 2024 8:25 AM
> To: dev@dpdk.org
> Cc: gakhil@marvell.com; Power, Ciara <ciara.power@intel.com>; Kusztal,
> ArkadiuszX <arkadiuszx.kusztal@intel.com>; stable@dpdk.org
> Subject: [PATCH] crypto/qat: fix ccm null aad pointer segfault
>
> This commit fixes a segfault, that occurs when NULL pointer is being set to the
> aad pointer field.
>
> Fixes: a815a04cea05 ("crypto/qat: support symmetric build op request")
> Cc: stable@dpdk.org
>
> Signed-off-by: Arkadiusz Kusztal <arkadiuszx.kusztal@intel.com>
> ---
> drivers/crypto/qat/dev/qat_crypto_pmd_gens.h | 10 ++++++----
> 1 file changed, 6 insertions(+), 4 deletions(-)
>
The CI fail looks to be unrelated to this patch:
70/112 DPDK:fast-tests / pcapng_autotest FAIL 6.39s (exit status 255 or signal 127 SIGinvalid)
Ok: 101
Expected Fail: 0
Fail: 1
Acked-by: Ciara Power <ciara.power@intel.com>
next prev parent reply other threads:[~2024-03-11 14:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-08 8:25 Arkadiusz Kusztal
2024-03-11 14:35 ` Power, Ciara [this message]
2024-03-13 14:51 ` 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=SN7PR11MB7639EBE1D9C4EF43E65DB631E6242@SN7PR11MB7639.namprd11.prod.outlook.com \
--to=ciara.power@intel.com \
--cc=arkadiuszx.kusztal@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).