From: David Marchand <david.marchand@redhat.com>
To: dev@dpdk.org
Cc: gmuthukrishn@marvell.com, gakhil@marvell.com,
Maxime Coquelin <maxime.coquelin@redhat.com>,
Chenbo Xia <chenbox@nvidia.com>
Subject: [PATCH] vhost: make cryptodev support optional
Date: Wed, 14 Oct 2026 18:31:38 +0200 [thread overview]
Message-ID: <20261014163138.1639970-1-david.marchand@redhat.com> (raw)
The vhost crypto part has seen CVEs in the past and is getting a lot of
eyes those days.
Contrary to the vhost async datapath code, the cryptodev code seems to
have active contributors, so dropping this code does not seem a good
thing.
This change here allows to keep this support, yet disable it for
uninterested parties.
Signed-off-by: David Marchand <david.marchand@redhat.com>
---
lib/vhost/meson.build | 10 +++++++---
1 file changed, 7 insertions(+), 3 deletions(-)
diff --git a/lib/vhost/meson.build b/lib/vhost/meson.build
index 6a24981d10..93366a9609 100644
--- a/lib/vhost/meson.build
+++ b/lib/vhost/meson.build
@@ -30,7 +30,6 @@ sources = files(
'vdpa.c',
'vduse.c',
'vhost.c',
- 'vhost_crypto.c',
'vhost_user.c',
'virtio_net.c',
'virtio_net_ctrl.c',
@@ -39,9 +38,14 @@ headers = files(
'rte_vdpa.h',
'rte_vhost.h',
'rte_vhost_async.h',
- 'rte_vhost_crypto.h',
)
driver_sdk_headers = files(
'vdpa_driver.h',
)
-deps += ['ethdev', 'cryptodev', 'hash', 'pci', 'dmadev']
+deps += ['ethdev', 'pci', 'dmadev']
+
+if dpdk_conf.has('RTE_LIB_CRYPTODEV')
+ sources += files('vhost_crypto.c')
+ headers += files('rte_vhost_crypto.h')
+ deps += ['cryptodev', 'hash']
+endif
--
2.54.0
next reply other threads:[~2026-10-14 16:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-14 16:31 David Marchand [this message]
2026-10-14 16:36 ` [PATCH] vhost: make cryptodev support optional Bruce Richardson
2026-10-14 16:47 ` [EXTERNAL] " Akhil Goyal
2026-10-20 11:22 ` Maxime Coquelin
2026-10-20 11:50 ` 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=20261014163138.1639970-1-david.marchand@redhat.com \
--to=david.marchand@redhat.com \
--cc=chenbox@nvidia.com \
--cc=dev@dpdk.org \
--cc=gakhil@marvell.com \
--cc=gmuthukrishn@marvell.com \
--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