From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/cryptodev Bug 1966] crypto-perf application segmentation faults where it previously didn't
Date: Wed, 08 Jul 2026 20:13:16 +0000 [thread overview]
Message-ID: <bug-1966-3@http.bugs.dpdk.org/> (raw)
http://bugs.dpdk.org/show_bug.cgi?id=1966
Bug ID: 1966
Summary: crypto-perf application segmentation faults where it
previously didn't
Product: DPDK
Version: 26.07
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: major
Priority: Normal
Component: cryptodev
Assignee: dev@dpdk.org
Reporter: abailey@iol.unh.edu
Target Milestone: ---
Running the dpdk-crypto-perf application with the following args creates a
segmentation fault. I am testing on an Intel QAT 8970 on an aarch64 system with
a single virtual function bound to vfio-pci. To the best of my knowledge, this
was not seen in testing prior to the merge of 26.07-rc2.
sudo ./dpdk-test-crypto-perf
-l 1-2
-n 4
--file-prefix=dpdk_1_20260708200005
-a 0000:03:01.0
--
--aead-aad-sz=16
--aead-algo=aes-gcm
--aead-iv-sz=12
--aead-key-sz=16
--aead-op=encrypt
--buffer-sz=64,512,2048
--devtype=crypto_qat
--digest-sz=16
--optype=aead
--ptest=throughput
--silent
--total-ops=10000000'
' returned a non-zero exit code: 139
16:00:57 Stderr: EAL: Detected CPU lcores: 160
16:00:57 EAL: Detected NUMA nodes: 2
16:00:57 EAL: Detected static linkage of DPDK
16:00:57 EAL: Multi-process socket
/var/run/dpdk/dpdk_1_20260708200005/mp_socket
16:00:57 EAL: Selected IOVA mode 'PA'
16:00:57 EAL: VFIO support initialized
16:00:57 EAL: Using IOMMU type 1 (Type 1)
16:00:57 CRYPTODEV: Creating cryptodev 0000:03:01.0_qat_asym
16:00:57 CRYPTODEV: Initialisation parameters - name:
0000:03:01.0_qat_asym,socket id: 0, max queue pairs: 0
16:00:57 CRYPTODEV: Creating cryptodev 0000:03:01.0_qat_sym
16:00:57 CRYPTODEV: Initialisation parameters - name:
0000:03:01.0_qat_sym,socket id: 0, max queue pairs: 0
16:00:57 Segmentation fault (core dumped)
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2026-07-08 20:13 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=bug-1966-3@http.bugs.dpdk.org/ \
--to=bugzilla@dpdk.org \
--cc=dev@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