From: Akhil Goyal <gakhil@marvell.com>
To: Nithinsen Kaithakadan <nkaithakadan@marvell.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: Anoob Joseph <anoobj@marvell.com>,
Tejasree Kondoj <ktejasree@marvell.com>,
"kai.ji@intel.com" <kai.ji@intel.com>,
"ciara.power@intel.com" <ciara.power@intel.com>,
"pablo.de.lara.guarch@intel.com" <pablo.de.lara.guarch@intel.com>,
"arkadiuszx.kusztal@intel.com" <arkadiuszx.kusztal@intel.com>,
dpdk stable <stable@dpdk.org>
Subject: RE: [PATCH] test/crypto: fix for mbuf sanity check failure
Date: Wed, 1 Oct 2025 07:43:03 +0000 [thread overview]
Message-ID: <CO6PR18MB4484031CA962CCEE5D416EE7D8E6A@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <20250923142254.1904208-1-nkaithakadan@marvell.com>
> Subject: [PATCH] test/crypto: fix for mbuf sanity check failure
>
> This patch resolves the following mbuf sanity check errors.
> - updating nb_segs and pkt_len in the head mbuf after
> freeing intermediate nodes in the chain.
> - fix incorrect usage of rte_pktmbuf_append by ensuring
> the head mbuf is passed instead of an intermediate
> node, allowing proper tail detection and metadata
> update.
>
> Fixes: dc3f6c5347b2 ("test/crypto: fix wireless auth digest segment")
> Fixes: 43220096d66a ("test/crypto: add PDCP cases for scatter gather")
> Fixes: dcdd01691f39 ("test/crypto: add GMAC SGL")
> Fixes: f3dbf94be60c ("app/test: check SGL on QAT")
Cc: stable@dpdk.org
>
> Signed-off-by: Nithinsen Kaithakadan <nkaithakadan@marvell.com>
Acked-by: Akhil Goyal <gakhil@marvell.com>
Applied to dpdk-next-crypto
Thanks.
prev parent reply other threads:[~2025-10-01 7:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-23 14:22 Nithinsen Kaithakadan
2025-10-01 7:43 ` 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=CO6PR18MB4484031CA962CCEE5D416EE7D8E6A@CO6PR18MB4484.namprd18.prod.outlook.com \
--to=gakhil@marvell.com \
--cc=anoobj@marvell.com \
--cc=arkadiuszx.kusztal@intel.com \
--cc=ciara.power@intel.com \
--cc=dev@dpdk.org \
--cc=kai.ji@intel.com \
--cc=ktejasree@marvell.com \
--cc=nkaithakadan@marvell.com \
--cc=pablo.de.lara.guarch@intel.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).