DPDK patches and discussions
 help / color / mirror / Atom feed
From: Akhil Goyal <gakhil@marvell.com>
To: Shani Peretz <shperetz@nvidia.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "stephen@networkplumber.org" <stephen@networkplumber.org>,
	"stable@dpdk.org" <stable@dpdk.org>, Kai Ji <kai.ji@intel.com>,
	Declan Doherty <declan.doherty@intel.com>,
	Marcin Kerlin <marcinx.kerlin@intel.com>,
	Slawomir Mrozowicz <slawomirx.mrozowicz@intel.com>,
	Michal Kobylinski <michalx.kobylinski@intel.com>,
	Piotr Azarewicz <piotr.azarewicz@intel.com>
Subject: RE: [EXTERNAL] [PATCH v2] app/crypto-perf: fix plaintext size exceeds buffer size
Date: Wed, 1 Oct 2025 07:48:46 +0000	[thread overview]
Message-ID: <CO6PR18MB44842A90E66252947FB6C21ED8E6A@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <20250825071450.25314-1-shperetz@nvidia.com>

> When test vector plaintext exceeds buffer size, only the first
> max_buffer_size bytes are processed, causing incorrect digest
> verification (computed vs expected mismatch).
> 
> This patch fixes this issue by checking that the plaintext size is
> larger than the buffer size and returns an error with a log.
> 
> Fixes: f8be1786b1b8 ("app/crypto-perf: introduce performance test application")
> Cc: stable@dpdk.org
> 
> Signed-off-by: Shani Peretz <shperetz@nvidia.com>
Acked-by: Akhil Goyal <gakhil@marvell.com>

Applied to dpdk-next-crypto
Thanks.

  parent reply	other threads:[~2025-10-01  7:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-05  6:38 [PATCH] " Shani Peretz
2025-08-05 15:49 ` Stephen Hemminger
2025-08-25  7:14 ` [PATCH v2] " Shani Peretz
2025-09-18  8:15   ` Shani Peretz
2025-10-01  7:48   ` Akhil Goyal [this message]
2025-09-03 15:45 ` [PATCH] " Ji, Kai

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=CO6PR18MB44842A90E66252947FB6C21ED8E6A@CO6PR18MB4484.namprd18.prod.outlook.com \
    --to=gakhil@marvell.com \
    --cc=declan.doherty@intel.com \
    --cc=dev@dpdk.org \
    --cc=kai.ji@intel.com \
    --cc=marcinx.kerlin@intel.com \
    --cc=michalx.kobylinski@intel.com \
    --cc=piotr.azarewicz@intel.com \
    --cc=shperetz@nvidia.com \
    --cc=slawomirx.mrozowicz@intel.com \
    --cc=stable@dpdk.org \
    --cc=stephen@networkplumber.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).