From: Fan Zhang <roy.fan.zhang@intel.com>
To: dev@dpdk.org
Cc: daxuex.gao@intel.com, maxime.coquelin@redhat.com,
Fan Zhang <roy.fan.zhang@intel.com>
Subject: [PATCH] vhost/crypto: fix failed compile
Date: Thu, 19 May 2022 16:07:11 +0000 [thread overview]
Message-ID: <20220519160711.159618-1-roy.fan.zhang@intel.com> (raw)
Fixes: 3c79609fda7c ("vhost/crypto: handle virtually non-contiguous buffers")
Cc: roy.fan.zhang@intel.com
This patch fixes the vhost crypto compile file on GCC12.
Ref. https://bugs.dpdk.org/show_bug.cgi?id=1011
The fix involves replacing rte_memcpy to memcpy.
Signed-off-by: Fan Zhang <roy.fan.zhang@intel.com>
---
lib/vhost/vhost_crypto.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/lib/vhost/vhost_crypto.c b/lib/vhost/vhost_crypto.c
index b1c0eb6a0f..278f990280 100644
--- a/lib/vhost/vhost_crypto.c
+++ b/lib/vhost/vhost_crypto.c
@@ -585,7 +585,7 @@ copy_data(void *dst_data, struct vhost_crypto_data_req *vc_req,
if (unlikely(!src || !dlen))
return -1;
- rte_memcpy((uint8_t *)data, src, dlen);
+ memcpy((uint8_t *)data, src, dlen);
data += dlen;
if (unlikely(dlen < to_copy)) {
--
2.34.1
reply other threads:[~2022-05-19 16:09 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=20220519160711.159618-1-roy.fan.zhang@intel.com \
--to=roy.fan.zhang@intel.com \
--cc=daxuex.gao@intel.com \
--cc=dev@dpdk.org \
--cc=maxime.coquelin@redhat.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).