DPDK patches and discussions
 help / color / mirror / Atom feed
From: Akhil Goyal <gakhil@marvell.com>
To: Gowrishankar Muthukrishnan <gmuthukrishn@marvell.com>,
	"dev@dpdk.org" <dev@dpdk.org>, Fan Zhang <fanzhang.oss@gmail.com>,
	Shally Verma <shallyv@marvell.com>,
	Ayuj Verma <ayverma@marvell.com>,
	Arkadiusz Kusztal <arkadiuszx.kusztal@intel.com>,
	Kanaka Durga Kotamarthy <kkotamarthy@marvell.com>
Cc: Anoob Joseph <anoobj@marvell.com>,
	Gowrishankar Muthukrishnan <gmuthukrishn@marvell.com>,
	"stable@dpdk.org" <stable@dpdk.org>
Subject: RE: [PATCH 3/3] test/crypto: fix RSA decrypt op validation
Date: Wed, 25 Jun 2025 11:48:19 +0000	[thread overview]
Message-ID: <CO6PR18MB448484AEBA90EB8329A93E79D87BA@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <20250620081921.2145-3-gmuthukrishn@marvell.com>

> Subject: [PATCH 3/3] test/crypto: fix RSA decrypt op validation
> 
> 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: 5ae36995f10f ("test/crypto: move RSA enqueue/dequeue into functions")
> Cc: stable@dpdk.org
> 
> Signed-off-by: Gowrishankar Muthukrishnan <gmuthukrishn@marvell.com>
Series Applied to dpdk-next-crypto
Thanks.

      parent reply	other threads:[~2025-06-25 11:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-20  8:19 [PATCH 1/3] crypto/openssl: include private exponent in RSA session Gowrishankar Muthukrishnan
2025-06-20  8:19 ` [PATCH 2/3] test/crypto: fix RSA test vector as per RFC 8017 Gowrishankar Muthukrishnan
2025-06-20  8:19 ` [PATCH 3/3] test/crypto: fix RSA decrypt op validation Gowrishankar Muthukrishnan
2025-06-24 13:55   ` Akhil Goyal
2025-06-25 11:48   ` 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=CO6PR18MB448484AEBA90EB8329A93E79D87BA@CO6PR18MB4484.namprd18.prod.outlook.com \
    --to=gakhil@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=gmuthukrishn@marvell.com \
    --cc=kkotamarthy@marvell.com \
    --cc=shallyv@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).