From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 44] examples/l2fwd-crypto : Wrong data length in case of AEAD ciphers
Date: Wed, 09 May 2018 12:43:52 +0000 [thread overview]
Message-ID: <bug-44-3@http.dpdk.org/tracker/> (raw)
https://dpdk.org/tracker/show_bug.cgi?id=44
Bug ID: 44
Summary: examples/l2fwd-crypto : Wrong data length in case of
AEAD ciphers
Product: DPDK
Version: 18.05
Hardware: All
OS: All
Status: CONFIRMED
Severity: normal
Priority: Normal
Component: examples
Assignee: dev@dpdk.org
Reporter: ankur.dwivedi@cavium.com
Target Milestone: ---
In l2fwd-crypto application, file main.c , the digest length is not getting
decremented for AEAD ciphers.
Line 410:
if (cparams->do_hash && cparams->hash_verify)
data_len -= cparams->digest_length;
I think this results in wrong values assignment in line 517
op->sym->aead.data.length = data_len;
and wrong digest data pointer assignment in line 524
op->sym->aead.digest.data = rte_pktmbuf_mtod(m,
uint8_t *) + ipdata_offset + data_len;
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2018-05-09 12:43 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=bug-44-3@http.dpdk.org/tracker/ \
--to=bugzilla@dpdk.org \
--cc=dev@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.