From: Fan Zhang <roy.fan.zhang@intel.com>
To: dev@dpdk.org
Cc: maxime.coquelin@redhat.com, tiwei.bie@intel.com
Subject: [dpdk-dev] [PATCH 0/2] vhost/crypto: some fixes
Date: Fri, 4 Jan 2019 11:22:44 +0000 [thread overview]
Message-ID: <20190104112246.9338-1-roy.fan.zhang@intel.com> (raw)
This patchset fixes two possible issues in vhost crypto. They are:
- The possible dead loop issue
- The out of bound access issue.
The fixes are in line with the following patchset
"[dpdk-dev] [PATCH 0/6] Some fixes for vhost"
(https://mails.dpdk.org/archives/dev/2019-January/122372.html)
Fan Zhang (2):
vhost/crypto: fix possible dead loop
vhost/crypto: fix possible out of bound access
lib/librte_vhost/vhost_crypto.c | 140 ++++++++++++++++++++++++++++------------
1 file changed, 100 insertions(+), 40 deletions(-)
--
2.13.6
next reply other threads:[~2019-01-04 11:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-04 11:22 Fan Zhang [this message]
2019-01-04 11:22 ` [dpdk-dev] [PATCH 1/2] vhost/crypto: fix possible dead loop Fan Zhang
2019-01-04 17:23 ` Maxime Coquelin
2019-01-04 11:22 ` [dpdk-dev] [PATCH 2/2] vhost/crypto: fix possible out of bound access Fan Zhang
2019-01-04 17:24 ` Maxime Coquelin
2019-01-04 18:00 ` [dpdk-dev] [PATCH 0/2] vhost/crypto: some fixes 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=20190104112246.9338-1-roy.fan.zhang@intel.com \
--to=roy.fan.zhang@intel.com \
--cc=dev@dpdk.org \
--cc=maxime.coquelin@redhat.com \
--cc=tiwei.bie@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).