From: Akhil Goyal <gakhil@marvell.com>
To: Nithin Kumar Dabilpuram <ndabilpuram@marvell.com>,
Fan Zhang <fanzhang.oss@gmail.com>
Cc: Jerin Jacob Kollanukkaran <jerinj@marvell.com>,
"dev@dpdk.org" <dev@dpdk.org>,
Nithin Kumar Dabilpuram <ndabilpuram@marvell.com>
Subject: RE: [PATCH] app/test: handle error packets from inline IPsec
Date: Thu, 16 Mar 2023 18:26:26 +0000 [thread overview]
Message-ID: <CO6PR18MB448476EF7B589E0F8D859D54D8BC9@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <20230309115339.1677916-1-ndabilpuram@marvell.com>
> Subject: [PATCH] app/test: handle error packets from inline IPsec
>
> In inline IPsec path, when the ol_flags indicate error, pkt might
> be incomplete. Hence don't trust the m->pkt_len to determine the
> size of packet, rather consider even data length's per segment.
>
> Signed-off-by: Nithin Dabilpuram <ndabilpuram@marvell.com>
> ---
Acked-by: Akhil Goyal <gakhil@marvell.com>
Applied to dpdk-next-crypto
Thanks.
prev parent reply other threads:[~2023-03-16 18:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-09 11:53 Nithin Dabilpuram
2023-03-16 18:26 ` 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=CO6PR18MB448476EF7B589E0F8D859D54D8BC9@CO6PR18MB4484.namprd18.prod.outlook.com \
--to=gakhil@marvell.com \
--cc=dev@dpdk.org \
--cc=fanzhang.oss@gmail.com \
--cc=jerinj@marvell.com \
--cc=ndabilpuram@marvell.com \
/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).