From: Akhil Goyal <gakhil@marvell.com>
To: Vikash Poddar <vikash.chandrax.poddar@intel.com>,
Kai Ji <kai.ji@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"stable@dpdk.org" <stable@dpdk.org>,
"arkadiuszx.kusztal@intel.com" <arkadiuszx.kusztal@intel.com>,
Ciara Power <ciara.power@intel.com>
Subject: RE: [EXT] [PATCH v7 1/3] common/qat: fix qat_dev_cmd_param corruption
Date: Tue, 20 Jun 2023 07:33:10 +0000 [thread overview]
Message-ID: <CO6PR18MB4484FEB81CC45A3862B76DC2D85CA@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <20230616140054.405194-1-vikash.chandrax.poddar@intel.com>
> Adding fix to address the memory corruption issue for
> qat_dev_cmd_param structure on QAT GEN3.
>
> This fix aligns the storage where it stores the value
> on 4 byte unsigned integer data type after
> reading slice configuration of QAT capabilities.
>
> Fixes: b3cbbcdffa4f ("common/qat: read HW slice configuration")
> Cc: stable@dpdk.org
> Cc: arkadiuszx.kusztal@intel.com
>
> Signed-off-by: Vikash Poddar <vikash.chandrax.poddar@intel.com>
> Acked-by: Ciara Power <ciara.power@intel.com>
Series
Applied to dpdk-next-crypto
Thanks.
prev parent reply other threads:[~2023-06-20 7:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-20 9:58 [PATCH] crypto/qat: support to enable insecure algorithms Vikash Poddar
2023-05-23 9:14 ` [PATCH v2] " Vikash Poddar
2023-05-23 14:35 ` Ji, Kai
2023-05-25 7:56 ` [EXT] " Akhil Goyal
2023-05-25 16:10 ` [PATCH v3] " Vikash Poddar
2023-05-26 6:48 ` [PATCH v4] " Vikash Poddar
2023-05-29 6:32 ` [PATCH v5] " Vikash Poddar
2023-05-29 10:45 ` [PATCH v6] " Vikash Poddar
2023-06-08 13:14 ` Power, Ciara
2023-06-14 18:30 ` [EXT] " Akhil Goyal
2023-06-16 14:00 ` [PATCH v7 1/3] common/qat: fix qat_dev_cmd_param corruption Vikash Poddar
2023-06-16 14:00 ` [PATCH v7 2/3] crypto/qat: support to enable insecure algorithms Vikash Poddar
2023-06-16 14:00 ` [PATCH v7 3/3] test/crypto: skip asym test for " Vikash Poddar
2023-06-20 7:33 ` Akhil Goyal [this message]
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=CO6PR18MB4484FEB81CC45A3862B76DC2D85CA@CO6PR18MB4484.namprd18.prod.outlook.com \
--to=gakhil@marvell.com \
--cc=arkadiuszx.kusztal@intel.com \
--cc=ciara.power@intel.com \
--cc=dev@dpdk.org \
--cc=kai.ji@intel.com \
--cc=stable@dpdk.org \
--cc=vikash.chandrax.poddar@intel.com \
/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).