From: coolwilled <coolwilled@gmail.com>
To: Hemant Agrawal <hemant.agrawal@nxp.com>,
sachin.saxena@oss.nxp.com, dev@dpdk.org, users@dpdk.org,
Gagandeep Singh <g.singh@nxp.com>
Subject: Is it a Bug? DPAA_SEC-test_cryptodev : output packet length is wrong !
Date: Tue, 30 Dec 2025 22:05:22 +0800 [thread overview]
Message-ID: <CAL2ZP-Any0B5btH4b5deqYytJrD-w+x_utS6KQ2KZase4d3MWQ@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 430 bytes --]
Hi,
I run command "cryptodev_dpaa_sec_autotest" in app/test/test_cryptodev.c in
DPDK v25.11. The output mbuf->pkt_len is wrong in the case :
TEST_PDCP_COUNT(uplane_encap_with_integrity(18, UPLINK, SNOW_ENC,
AES_AUTH));
from test_PDCP_PROTO_uplane_encap_all()
from test_PDCP_PROTO_all().
In this case, in test_pdcp_proto(), the output
ut_params->ibuf->data_len/pkt_len = 73.
The pkt_len is wrong, it should be 71.
Thanks a lot !
[-- Attachment #2: Type: text/html, Size: 600 bytes --]
reply other threads:[~2025-12-30 14:05 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CAL2ZP-Any0B5btH4b5deqYytJrD-w+x_utS6KQ2KZase4d3MWQ@mail.gmail.com \
--to=coolwilled@gmail.com \
--cc=dev@dpdk.org \
--cc=g.singh@nxp.com \
--cc=hemant.agrawal@nxp.com \
--cc=sachin.saxena@oss.nxp.com \
--cc=users@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).