From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: Fan Zhang <roy.fan.zhang@intel.com>, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v2] vhost/crypto: fix incorrect copy
Date: Fri, 9 Nov 2018 15:31:09 +0100 [thread overview]
Message-ID: <e26cde15-cc45-2591-b96a-17546d6cd413@redhat.com> (raw)
In-Reply-To: <20181106162248.5172-1-roy.fan.zhang@intel.com>
On 11/6/18 5:22 PM, Fan Zhang wrote:
> This patch fixes the incorrect packet content copy in the
> chaining mode. Originally the content before cipher offset is
> overwritten by all zeros. This patch fixes the problem by
> making sure the correct write back source and destination
> settings during set up.
>
> Signed-off-by: Fan Zhang <roy.fan.zhang@intel.com>
> ---
> v2:
> - fixed a write back size error bug.
>
> lib/librte_vhost/vhost_crypto.c | 460 ++++++++++++++++++++++++++++++----------
> 1 file changed, 348 insertions(+), 112 deletions(-)
>
Reviewed-by: Maxime Coquelin <maxime.coquelin@redhat.com>
Thanks,
Maxime
next prev parent reply other threads:[~2018-11-09 14:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-24 13:18 [dpdk-dev] [PATCH] " Fan Zhang
2018-10-30 8:56 ` Maxime Coquelin
2018-11-06 16:22 ` [dpdk-dev] [PATCH v2] " Fan Zhang
2018-11-09 14:31 ` Maxime Coquelin [this message]
2018-11-09 14:51 ` Maxime Coquelin
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=e26cde15-cc45-2591-b96a-17546d6cd413@redhat.com \
--to=maxime.coquelin@redhat.com \
--cc=dev@dpdk.org \
--cc=roy.fan.zhang@intel.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).