From: "Power, Ciara" <ciara.power@intel.com>
To: "Dooley, Brian" <brian.dooley@intel.com>, "Ji, Kai" <kai.ji@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"gakhil@marvell.com" <gakhil@marvell.com>,
"Dooley, Brian" <brian.dooley@intel.com>
Subject: RE: [PATCH v1] crypto/qat: fix struct alignment
Date: Fri, 30 Jun 2023 21:19:37 +0000 [thread overview]
Message-ID: <SN7PR11MB763901A5600EF01F2DC87710E62AA@SN7PR11MB7639.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20230630113040.521683-1-brian.dooley@intel.com>
> -----Original Message-----
> From: Brian Dooley <brian.dooley@intel.com>
> Sent: Friday 30 June 2023 12:31
> To: Ji, Kai <kai.ji@intel.com>
> Cc: dev@dpdk.org; gakhil@marvell.com; Dooley, Brian
> <brian.dooley@intel.com>
> Subject: [PATCH v1] crypto/qat: fix struct alignment
>
> The qat_sym_session struct variable alignment was causing a segfault.
> AES expansion keys require 16-byte alignment. Added __rte_aligned to the
> expansion keys.
>
> Fixes: ca0ba0e48129 ("crypto/qat: default to IPsec MB for computations")
>
> Signed-off-by: Brian Dooley <brian.dooley@intel.com>
> ---
Acked-by: Ciara Power <ciara.power@intel.com>
next prev parent reply other threads:[~2023-06-30 21:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-30 11:30 Brian Dooley
2023-06-30 21:19 ` Power, Ciara [this message]
2023-07-03 14:15 ` 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=SN7PR11MB763901A5600EF01F2DC87710E62AA@SN7PR11MB7639.namprd11.prod.outlook.com \
--to=ciara.power@intel.com \
--cc=brian.dooley@intel.com \
--cc=dev@dpdk.org \
--cc=gakhil@marvell.com \
--cc=kai.ji@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).