From: Gowrishankar Muthukrishnan <gmuthukrishn@marvell.com>
To: "Ji, Kai" <kai.ji@intel.com>
Cc: Anoob Joseph <anoobj@marvell.com>, "dev@dpdk.org" <dev@dpdk.org>,
Akhil Goyal <gakhil@marvell.com>,
Fan Zhang <fanzhang.oss@gmail.com>,
Shally Verma <shallyv@marvell.com>,
Kanaka Durga Kotamarthy <kkotamarthy@marvell.com>,
Ayuj Verma <ayverma@marvell.com>,
"Kusztal, ArkadiuszX" <arkadiuszx.kusztal@intel.com>
Subject: RE: [PATCH] test/crypto: fix RSA decrypt op validation
Date: Wed, 18 Jun 2025 16:04:49 +0000 [thread overview]
Message-ID: <CO1PR18MB47144653AC9A8DF6E8B1C697CB72A@CO1PR18MB4714.namprd18.prod.outlook.com> (raw)
In-Reply-To: <DS0PR11MB7458F54FAE4573EEA5D30AEF8170A@DS0PR11MB7458.namprd11.prod.outlook.com>
Hi Kai Ji,
>
> Hi Gowrishankar,
>
> Thanks for reach out, I don't have those environments setup on my end, but
> Ubuntu 20.04 and RHEL8 are old but still common LTS packages.
> Are you able to dump the actual msg buffer ?
>
RSA_private_decrypt fails and return code is -1. Output buffer is untouched.
I dumped error code of it:
error:04067084:rsa routines:rsa_ossl_public_decrypt:data too large for modulus
When I used same openssl library that I compiled, no error is seen. Also, public
decrypt function is called, but it should be private decrypt to be called.
JFYI end of life for full support already over for the above distros. Not sure if the
Openssl 1.1.1 in them need some fix for above.
Thanks,
Gowrishankar
> It is highly possible relates to dsitro-specific patches ? Paddings ? Or crypto
> polices in RHEL ?
>
> Regards
>
> Kai
>
> ________________________________
>
> From: Gowrishankar Muthukrishnan <gmuthukrishn@marvell.com>
> Sent: Thursday, June 12, 2025 11:33
> To: Ji, Kai <kai.ji@intel.com>
> Cc: Anoob Joseph <anoobj@marvell.com>; dev@dpdk.org <dev@dpdk.org>; Akhil
> Goyal <gakhil@marvell.com>; Fan Zhang <fanzhang.oss@gmail.com>; Shally
> Verma <shallyv@marvell.com>; Kanaka Durga Kotamarthy
> <kkotamarthy@marvell.com>; Ayuj Verma <ayverma@marvell.com>; Kusztal,
> ArkadiuszX <arkadiuszx.kusztal@intel.com>
> Subject: RE: [PATCH] test/crypto: fix RSA decrypt op validation
>
> Hi Kai Ji,
> This patch adds a check on cop status after DECRYPT in existing RSA test.There
> are few CI failures for this patch and the failures are very specific to Openssl 1.1.1
> variants used in below platforms:
> * Ubuntu 20.04 - Openssl 1.1.1f
> * RHEL 8 - Openssl 1.1.1k
>
> When I manually build these Openssl variants in the above platforms (using
> Docker images) and execute tests using respective openssl shared libraries, all
> tests PASS. If I use Openssl library that is shipped within the above distributions,
> the test in patch FAIL.
>
> I would like to get your opinion first to proceed on getting these patches CI acked.
> In my debug, I don't see any issue with the patch and the patch adds better
> Validation indeed. May be that, it has uncovered a potential failure in above
> Distros. Can you check on your end if these failures disappear in manual try.
> What would you suggest to go forward, for openssl PMD ?
>
> If required, I can start filing a Bugzilla as well.
>
> Thanks,
> Gowrishankar
>
> >
> > Following RSA encrypt op, same plaintext buffer is used as output
> > buffer for decrypt op, hence comparing plaintext buffer against same
> > buffer pointer in crypto op always succeed irrespective of whether decrypt op
> succeeds or not.
> > This patch fixes this issue with a local buffer for crypto op.
> >
> > Fixes: 5ae36995f10 ("test/crypto: move RSA enqueue/dequeue into
> > functions")
> > Cc: stable@dpdk.org
> >
> > Signed-off-by: Gowrishankar Muthukrishnan <gmuthukrishn@marvell.com>
>
prev parent reply other threads:[~2025-06-18 16:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-10 10:44 Gowrishankar Muthukrishnan
2025-05-28 8:38 ` Gowrishankar Muthukrishnan
2025-06-12 10:33 ` Gowrishankar Muthukrishnan
2025-06-16 14:17 ` Ji, Kai
2025-06-18 16:04 ` Gowrishankar Muthukrishnan [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=CO1PR18MB47144653AC9A8DF6E8B1C697CB72A@CO1PR18MB4714.namprd18.prod.outlook.com \
--to=gmuthukrishn@marvell.com \
--cc=anoobj@marvell.com \
--cc=arkadiuszx.kusztal@intel.com \
--cc=ayverma@marvell.com \
--cc=dev@dpdk.org \
--cc=fanzhang.oss@gmail.com \
--cc=gakhil@marvell.com \
--cc=kai.ji@intel.com \
--cc=kkotamarthy@marvell.com \
--cc=shallyv@marvell.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).