From: Akhil Goyal <gakhil@marvell.com>
To: Hemant Agrawal <hemant.agrawal@nxp.com>,
"dev@dpdk.org" <dev@dpdk.org>,
"roy.fan.zhang@intel.com" <roy.fan.zhang@intel.com>
Cc: "konstantin.ananyev@intel.com" <konstantin.ananyev@intel.com>,
Gagandeep Singh <g.singh@nxp.com>,
"marcinx.smoczynski@intel.com" <marcinx.smoczynski@intel.com>,
"stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-stable] [EXT] [PATCH 04/15] crypto: fix raw process for multi-seg case
Date: Mon, 6 Sep 2021 18:38:19 +0000 [thread overview]
Message-ID: <CO6PR18MB4484995B632770298AFE298FD8D29@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <20210825071510.7913-5-hemant.agrawal@nxp.com>
> From: Gagandeep Singh <g.singh@nxp.com>
>
> If no next segment available the “for” loop will fail and it still
> returns i+1 i.e. 2, which is wrong as it has filled only 1 buffer.
>
> Fixes: 7adf992fb9bf ("cryptodev: introduce CPU crypto API")
> Cc: marcinx.smoczynski@intel.com
> Cc: stable@dpdk.org
>
> Signed-off-by: Gagandeep Singh <g.singh@nxp.com>
@Fan: Could you please review this patch.
next prev parent reply other threads:[~2021-09-06 18:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210812071244.28799-1-hemant.agrawal@nxp.com>
[not found] ` <20210825071510.7913-1-hemant.agrawal@nxp.com>
2021-08-25 7:14 ` [dpdk-stable] " Hemant Agrawal
2021-09-06 18:38 ` Akhil Goyal [this message]
[not found] ` <20210907075957.28848-1-hemant.agrawal@nxp.com>
2021-09-07 7:59 ` [dpdk-stable] [PATCH v2 " Hemant Agrawal
[not found] ` <20211013190032.2308-1-hemant.agrawal@nxp.com>
2021-10-13 19:00 ` [dpdk-stable] [PATCH v4 " Hemant Agrawal
2021-10-15 17:39 ` Ananyev, Konstantin
[not found] ` <20211017161651.9220-1-hemant.agrawal@nxp.com>
2021-10-17 16:16 ` [dpdk-stable] [PATCH v5 " Hemant Agrawal
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=CO6PR18MB4484995B632770298AFE298FD8D29@CO6PR18MB4484.namprd18.prod.outlook.com \
--to=gakhil@marvell.com \
--cc=dev@dpdk.org \
--cc=g.singh@nxp.com \
--cc=hemant.agrawal@nxp.com \
--cc=konstantin.ananyev@intel.com \
--cc=marcinx.smoczynski@intel.com \
--cc=roy.fan.zhang@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).