From: "Zhang, Roy Fan" <roy.fan.zhang@intel.com>
To: Akhil Goyal <gakhil@marvell.com>, "Ji, Kai" <kai.ji@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "chandu@amd.com" <chandu@amd.com>
Subject: RE: [EXT] [dpdk-dev v5] crypto/openssl: openssl 3.0 support on sym crypto routine
Date: Fri, 25 Feb 2022 13:51:10 +0000 [thread overview]
Message-ID: <MW5PR11MB58091D0C2F7D37B50A9444F8B83E9@MW5PR11MB5809.namprd11.prod.outlook.com> (raw)
In-Reply-To: <PH0PR18MB4491591B14A3C7E071477C34D83E9@PH0PR18MB4491.namprd18.prod.outlook.com>
Hi Akhil,
> -----Original Message-----
> From: Akhil Goyal <gakhil@marvell.com>
> Sent: Friday, February 25, 2022 10:40 AM
> To: Ji, Kai <kai.ji@intel.com>; dev@dpdk.org
> Cc: Zhang, Roy Fan <roy.fan.zhang@intel.com>
> Subject: RE: [EXT] [dpdk-dev v5] crypto/openssl: openssl 3.0 support on sym
> crypto routine
>
> Hi Kai,
> >
> > The warning messages are deprecated APIs warnings from openssl , not
> > compiler warnings from gcc, the integrity of DPDK remain the same.
> > Alongside openssl pmd, the ccp and qat pmd also raise the same type of
> > warnings once openssl 3.0 installed.
> >
> > In the current intel roadmap, we will try to support 3.0 API fully for openssl
> and
> > qat pmds by the end of year, so this patch is the first step.
> > I think the warning messages are safe to stay, Unfortunately the fix ccp
> pmd
> > driver is out of our reach.
> >
>
> When DPDK is compiled with openssl 3.0. I am seeing these errors in
> compilation.
> So, compilation is broken and we cannot take this patch as is.
> We have few options,
> - fix all of these errors,
> - add exception in meson.build for ignoring these errors.
> - disable/skip compilation of PMDs if openssl version is >3.0
>
> Adding only one type of APIs does not make sense, if the driver is not
> compiled.
>
> In file included from ../drivers/crypto/openssl/openssl_pmd_private.h:12,
> from ../drivers/crypto/openssl/rte_openssl_pmd.c:16:
> /usr/local/include/openssl/dh.h:223:27: note: declared here
> 223 | OSSL_DEPRECATEDIN_3_0 int DH_generate_key(DH *dh);
> | ^~~~~~~~~~~~~~~
> ../drivers/crypto/openssl/rte_openssl_pmd.c: In function
> 'process_openssl_rsa_op':
> ../drivers/crypto/openssl/rte_openssl_pmd.c:2068:3: error:
> 'RSA_public_encrypt' is deprecated: Since OpenSSL 3.0 [-
> Werror=deprecated-declarations]
> 2068 | ret = RSA_public_encrypt(op->rsa.message.length,
You are right. We will defer the change to next release so we can send along
with the asym openssl change Kai is working on. But since we have your attention
I would want to drag Chandubabu's attention too as there are three PMDs uses
deprecated openssl lib APIs: openssl, qat, and ccp. Adding a suppress flag to meson
build file won't resolve the problem - we need to resolve them before the APIs are
gone for good.
>
> Also, avoid top posting of comments!
next prev parent reply other threads:[~2022-02-25 13:51 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-04 17:57 [dpdk-dev v1] crypto/openssl: openssl EVP MAC routine api update Kai Ji
2022-02-07 15:24 ` [dpdk-dev v2] crypto/openssl: openssl 3.0 support on sym MAC routine Kai Ji
2022-02-07 15:40 ` Zhang, Roy Fan
2022-02-17 17:45 ` [dpdk-dev v3] crypto/openssl: openssl 3.0 support on sym crypto routine Kai Ji
2022-02-17 18:01 ` [EXT] " Akhil Goyal
2022-02-18 9:44 ` [dpdk-dev v4] " Kai Ji
2022-02-18 11:51 ` [dpdk-dev v5] " Kai Ji
2022-02-18 13:41 ` Zhang, Roy Fan
2022-02-24 19:02 ` [EXT] " Akhil Goyal
2022-02-24 23:13 ` Ji, Kai
2022-02-25 3:55 ` Akhil Goyal
2022-02-25 10:19 ` Ji, Kai
2022-02-25 10:39 ` Akhil Goyal
2022-02-25 11:19 ` Ji, Kai
2022-02-25 13:51 ` Zhang, Roy Fan [this message]
2022-02-28 5:35 ` Namburu, Chandu-babu
2022-02-25 15:13 ` [dpdk-dev v6] " Kai Ji
2022-02-25 17:35 ` Stephen Hemminger
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=MW5PR11MB58091D0C2F7D37B50A9444F8B83E9@MW5PR11MB5809.namprd11.prod.outlook.com \
--to=roy.fan.zhang@intel.com \
--cc=chandu@amd.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).