From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id E7790464C4; Mon, 31 Mar 2025 09:26:29 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 706C440156; Mon, 31 Mar 2025 09:26:29 +0200 (CEST) Received: from inbox.dpdk.org (inbox.dpdk.org [95.142.172.178]) by mails.dpdk.org (Postfix) with ESMTP id 9BA8B40150 for ; Mon, 31 Mar 2025 09:26:27 +0200 (CEST) Received: by inbox.dpdk.org (Postfix, from userid 33) id 795CC464C5; Mon, 31 Mar 2025 09:26:27 +0200 (CEST) From: bugzilla@dpdk.org To: dev@dpdk.org Subject: [DPDK/vhost/virtio Bug 1685] [dpdk-22.11.8RC1] virtio_ipsec_cryptodev_func/test_aesni_mb_aes_cbc_sha1_hmac: dpdk-vhost_crypto Segmentation fault (core dumped) when launch qemu Date: Mon, 31 Mar 2025 07:26:27 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: DPDK X-Bugzilla-Component: vhost/virtio X-Bugzilla-Version: 22.11 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: yux.jiang@intel.com X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: dev@dpdk.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: Content-Type: multipart/alternative; boundary=17434059870.7d3b.250896 Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://bugs.dpdk.org/ Auto-Submitted: auto-generated X-Auto-Response-Suppress: All MIME-Version: 1.0 X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org --17434059870.7d3b.250896 Date: Mon, 31 Mar 2025 09:26:27 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.dpdk.org/ Auto-Submitted: auto-generated X-Auto-Response-Suppress: All https://bugs.dpdk.org/show_bug.cgi?id=3D1685 Bug ID: 1685 Summary: [dpdk-22.11.8RC1] virtio_ipsec_cryptodev_func/test_aesni_mb_aes_cbc_sha1 _hmac: dpdk-vhost_crypto Segmentation fault (core dumped) when launch qemu Product: DPDK Version: 22.11 Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: Normal Component: vhost/virtio Assignee: dev@dpdk.org Reporter: yux.jiang@intel.com Target Milestone: --- [Environment] DPDK version: commit 684d996a20 (HEAD -> v22.11.8-rc1, tag: v22.11.8-rc1, origin/22.11) version: 22.11.8-rc1 OS: Ubuntu 18.04.5 LTS (Bionic Beaver); 5.4.0-150-generic Compiler: gcc version 7.5.0 Hardware platform: Intel(R) Xeon(R) Platinum 8180 CPU @ 2.50GHz QEMU: qemu-2.12 qemu version >=3D 2.12 in qemu enable vhost-user-crypto: ./configure --target-list=3Dx86_64-softmmu --enable-vhost-crypto --prefix=3D/root/qemu-2.12 && make && make install Qemu version: 2.12 QAT: C62x Chipset QuickAssist Technology 37c8 [Test Setup] Steps to reproduce List the steps to reproduce the issue. 1, Build dpdk rm -rf x86_64-native-linuxapp-gcc CC=3Dgcc meson --werror -Denable_kmods=3DFalse -Dlibdir=3Dlib -Dexamples=3D= all --default-library=3Dstatic x86_64-native-linuxapp-gcc ninja -C x86_64-native-linuxapp-gcc -j 110 ls x86_64-native-linuxapp-gcc/examples/dpdk-vhost_crypto 2, Bind QAT device and run the dpdk vhost sample in HOST side usertools/dpdk-devbind.py --force --bind=3Dvfio-pci 0000:1a:01.0 0000:1c:01= .0 0000:1e:01.0 x86_64-native-linuxapp-gcc/examples/dpdk-vhost_crypto -l 1,2,3,4,5 -a 0000:1a:01.0 -a 0000:1c:01.0 -a 0000:1e:01.0 --vdev crypto_scheduler_pmd_1,worker=3D0000:1a:01.0_qat_sym,worker=3D0000:1c:01.0_= qat_sym,worker=3D0000:1e:01.0_qat_sym,mode=3Dround-robin,ordering=3Denable --socket-mem 2048,0 -n 4 -- --config "(2,0,0),(3,0,0),(4,0,0),(5,0,0)" --socket-file 2,/tmp/vm0_crypto0.sock=20=20=20=20=20=20=20 --socket-file=3D3,/tmp/vm0_crypto1.sock=20=20=20=20=20=20=20 --socket-file=3D4,/tmp/vm1_crypto0.sock=20=20=20=20=20=20=20 --socket-file=3D5,/tmp/vm1_crypto1.sock 3, Bind NIC PF to vfio-pci usertools/dpdk-devbind.py --bind=3Dvfio-pci 0000:60:00.0 0000:60:00.1 0000:3b:00.0 0000:3b:00.1 4, Start VM0 by the qemu: taskset -c 11,12,13,14 /usr/local/qemu-2.12.0/bin/qemu-system-x86_64 -name= vm0 -enable-kvm -pidfile /tmp/.vm0.pid -daemonize -monitor unix:/tmp/vm0_monitor.sock,server,nowait -device e1000,netdev=3Dnttsip1 -n= etdev user,id=3Dnttsip1,hostfwd=3Dtcp:10.67.118.199:6410-:22 -device vfio-pci,host=3D0000:3b:00.0,id=3Dpt_0 -device vfio-pci,host=3D0000:3b:00.1= ,id=3Dpt_1 -cpu host -smp 4 -m 4096 -object memory-backend-file,id=3Dmem,size=3D4096M,mem-path=3D/dev/hugepages,share= =3Don -numa node,memdev=3Dmem -mem-prealloc -chardev socket,path=3D/tmp/vm0_qga0.sock,server,nowait,id=3Dvm0_qga0 -device virtio= -serial -device virtserialport,chardev=3Dvm0_qga0,name=3Dorg.qemu.guest_agent.0 -vn= c :1 -chardev socket,path=3D/tmp/vm0_crypto0.sock,id=3Dvm0_crypto0 -object cryptodev-vhost-user,id=3Dcryptodev0,chardev=3Dvm0_crypto0 -device virtio-crypto-pci,id=3Dcrypto0,cryptodev=3Dcryptodev0 -chardev socket,path=3D/tmp/vm0_crypto1.sock,id=3Dvm0_crypto1 -object cryptodev-vhost-user,id=3Dcryptodev1,chardev=3Dvm0_crypto1 -device virtio-crypto-pci,id=3Dcrypto1,cryptodev=3Dcryptodev1 -drive file=3D/root/VMs/ubuntu2004-0.img [Actual Result] VM logs: root@dpdk-yaobing-purely147:~/dpdk# taskset -c 11,12,13,14 /usr/local/qemu-2.12.0/bin/qemu-system-x86_64 -name vm0 -enable-kvm -pidfi= le /tmp/.vm0.pid -daemonize -monitor unix:/tmp/vm0_monitor.sock,server,nowait -device e1000,netdev=3Dnttsip1 -netdev user,id=3Dnttsip1,hostfwd=3Dtcp:10.67.118.199:6010-:22 -device vfio-pci,host=3D0000:3b:00.0,id=3Dpt_0 -device vfio-pci,host=3D0000:3b:00.1= ,id=3Dpt_1 -cpu host -smp 4 -m 4096 -object memory-backend-file,id=3Dmem,size=3D4096M,mem-path=3D/dev/hugepages,share= =3Don -numa node,memdev=3Dmem -mem-prealloc -chardev socket,path=3D/tmp/vm0_qga0.sock,server,nowait,id=3Dvm0_qga0 -device virtio= -serial -device virtserialport,chardev=3Dvm0_qga0,name=3Dorg.qemu.guest_agent.0 -vn= c :1 -chardev socket,path=3D/tmp/vm0_crypto0.sock,id=3Dvm0_crypto0 -object cryptodev-vhost-user,id=3Dcryptodev0,chardev=3Dvm0_crypto0 -device virtio-crypto-pci,id=3Dcrypto0,cryptodev=3Dcryptodev0 -chardev socket,path=3D/tmp/vm0_crypto1.sock,id=3Dvm0_crypto1 -object cryptodev-vhost-user,id=3Dcryptodev1,chardev=3Dvm0_crypto1 -device virtio-crypto-pci,id=3Dcrypto1,cryptodev=3Dcryptodev1 -drive file=3D/root/VMs/ubuntu2004-0.img qemu-system-x86_64: -object cryptodev-vhost-user,id=3Dcryptodev0,chardev=3Dvm0_crypto0: Failed to read = msg header. Read 0 instead of 12. Original request 1. qemu-system-x86_64: -object cryptodev-vhost-user,id=3Dcryptodev0,chardev=3Dvm0_crypto0: failed to init vhost_crypto for queue 0 DPDK VHOST sample HOST log:=20 root@dpdk-yaobing-purely147:~/dpdk# x86_64-native-linuxapp-gcc/examples/dpdk-vhost_crypto -l 1,2,3,4,5 -a 0000:1a:01.0 -a 0000:1c:01.0 -a 0000:1e:01.0 --vdev crypto_scheduler_pmd_1,worker=3D0000:1a:01.0_qat_sym,worker=3D0000:1c:01.0_= qat_sym,worker=3D0000:1e:01.0_qat_sym,mode=3Dround-robin,ordering=3Denable --socket-mem 2048,0 -n 4 -- --config "(2,0,0),(3,0,0),(4,0,0),(5,0,0)" --socket-file 2,/tmp/vm0_crypto0.sock=20=20=20=20=20=20=20 --socket-file=3D3,/tmp/vm0_crypto1.sock=20=20=20=20=20=20=20 --socket-file=3D4,/tmp/vm1_crypto0.sock=20=20=20=20=20=20=20 --socket-file=3D5,/tmp/vm1_crypto1.sock EAL: Detected CPU lcores: 112 EAL: Detected NUMA nodes: 2 EAL: Detected static linkage of DPDK EAL: Multi-process socket /var/run/dpdk/rte/mp_socket EAL: Selected IOVA mode 'VA' EAL: VFIO support initialized EAL: Using IOMMU type 1 (Type 1) EAL: Probe PCI driver: qat (8086:37c9) device: 0000:1a:01.0 (socket 0) CRYPTODEV: Creating cryptodev 0000:1a:01.0_qat_sym CRYPTODEV: Initialisation parameters - name: 0000:1a:01.0_qat_sym,socket id= : 0, max queue pairs: 0 CRYPTODEV: Creating cryptodev 0000:1a:01.0_qat_asym CRYPTODEV: Initialisation parameters - name: 0000:1a:01.0_qat_asym,socket i= d: 0, max queue pairs: 0 EAL: Probe PCI driver: qat (8086:37c9) device: 0000:1c:01.0 (socket 0) CRYPTODEV: Creating cryptodev 0000:1c:01.0_qat_sym CRYPTODEV: Initialisation parameters - name: 0000:1c:01.0_qat_sym,socket id= : 0, max queue pairs: 0 CRYPTODEV: Creating cryptodev 0000:1c:01.0_qat_asym CRYPTODEV: Initialisation parameters - name: 0000:1c:01.0_qat_asym,socket i= d: 0, max queue pairs: 0 EAL: Probe PCI driver: qat (8086:37c9) device: 0000:1e:01.0 (socket 0) CRYPTODEV: Creating cryptodev 0000:1e:01.0_qat_sym CRYPTODEV: Initialisation parameters - name: 0000:1e:01.0_qat_sym,socket id= : 0, max queue pairs: 0 CRYPTODEV: Creating cryptodev 0000:1e:01.0_qat_asym CRYPTODEV: Initialisation parameters - name: 0000:1e:01.0_qat_asym,socket i= d: 0, max queue pairs: 0 CRYPTODEV: Creating cryptodev crypto_scheduler_pmd_1 CRYPTODEV: Initialisation parameters - name: crypto_scheduler_pmd_1,socket = id: 0, max queue pairs: 8 cryptodev_scheduler_create() line 140: Scheduling mode =3D round-robin cryptodev_scheduler_create() line 195: Packet ordering =3D enable USER1: Processing on Core 2 started VHOST_CONFIG: (/tmp/vm0_crypto0.sock) logging feature is disabled in async = copy mode VHOST_CONFIG: (/tmp/vm0_crypto0.sock) vhost-user server: socket created, fd= : 49 VHOST_CONFIG: (/tmp/vm0_crypto0.sock) binding succeeded CRYPTODEV: rte_cryptodev_start() line 1208: Device with dev_id=3D0 already started VHOST_CONFIG: (/tmp/vm0_crypto1.sock) logging feature is disabled in async = copy mode VHOST_CONFIG: (/tmp/vm0_crypto1.sock) vhost-user server: socket created, fd= : 53 USER1: Processing on Core 3 started VHOST_CONFIG: (/tmp/vm0_crypto1.sock) binding succeeded CRYPTODEV: rte_cryptodev_start() line 1208: Device with dev_id=3D0 already started VHOST_CONFIG: (/tmp/vm1_crypto0.sock) logging feature is disabled in async = copy mode VHOST_CONFIG: (/tmp/vm1_crypto0.sock) vhost-user server: socket created, fd= : 54 USER1: Processing on Core 4 started VHOST_CONFIG: (/tmp/vm1_crypto0.sock) binding succeeded CRYPTODEV: rte_cryptodev_start() line 1208: Device with dev_id=3D0 already started VHOST_CONFIG: (/tmp/vm1_crypto1.sock) logging feature is disabled in async = copy mode VHOST_CONFIG: (/tmp/vm1_crypto1.sock) vhost-user server: socket created, fd= : 55 USER1: Processing on Core 5 started VHOST_CONFIG: (/tmp/vm1_crypto1.sock) binding succeeded VHOST_CONFIG: (/tmp/vm0_crypto0.sock) new vhost user connection is 56 VHOST_CONFIG: (/tmp/vm0_crypto0.sock) new device, handle is 0 USER1: New Vhost-crypto Device /tmp/vm0_crypto0.sock, Device ID 0 Segmentation fault (core dumped) [Regression] Is this issue a regression: (Y/N) Y Bad commit id: 6816d998b0 examples/vhost_crypto: fix user callbacks commit 6816d998b04e26ca4468356e0a3c10daf65412eb Author: Gowrishankar Muthukrishnan Date: Fri Feb 28 19:17:11 2025 +0530 examples/vhost_crypto: fix user callbacks [ upstream commit f7cf44d49b1115238a87c5852db4b47290bfdc25 ] In order to handle new vhost user connection, use new_connection and destroy_connection callbacks. Fixes: f5188211c721 ("examples/vhost_crypto: add sample application") Signed-off-by: Gowrishankar Muthukrishnan Acked-by: Akhil Goyal Reviewed-by: Maxime Coquelin --=20 You are receiving this mail because: You are the assignee for the bug.= --17434059870.7d3b.250896 Date: Mon, 31 Mar 2025 09:26:27 +0200 MIME-Version: 1.0 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.dpdk.org/ Auto-Submitted: auto-generated X-Auto-Response-Suppress: All
Bug ID 1685
Summary [dpdk-22.11.8RC1] virtio_ipsec_cryptodev_func/test_aesni_mb_a= es_cbc_sha1_hmac: dpdk-vhost_crypto Segmentation fault (core dumped) when= launch qemu
Product DPDK
Version 22.11
Hardware All
OS All
Status UNCONFIRMED
Severity normal
Priority Normal
Component vhost/virtio
Assignee dev@dpdk.org
Reporter yux.jiang@intel.com
Target Milestone --- 

[Environment]

DPDK version: commit 684d996a20 (HEAD -> v22.11.8-rc1, tag: v22.11.8-rc1,
origin/22.11) version: 22.11.8-rc1
OS: Ubuntu 18.04.5 LTS (Bionic Beaver); 5.4.0-150-generic
Compiler: gcc version 7.5.0
Hardware platform: Intel(R) Xeon(R) Platinum 8180 CPU @ 2.50GHz
QEMU: qemu-2.12
qemu version >=3D 2.12 in qemu enable vhost-user-crypto:
        ./configure --target-list=3Dx86_64-softmmu --enable-vhost-crypto
--prefix=3D/root/qemu-2.12 && make && make install
Qemu version: 2.12
QAT: C62x Chipset QuickAssist Technology 37c8

[Test Setup]
Steps to reproduce
List the steps to reproduce the issue.

1, Build dpdk
rm -rf x86_64-native-linuxapp-gcc
CC=3Dgcc meson --werror -Denable_kmods=3DFalse -Dlibdir=3Dlib -Dexamples=3D=
all
--default-library=3Dstatic x86_64-native-linuxapp-gcc
ninja -C x86_64-native-linuxapp-gcc -j 110
ls x86_64-native-linuxapp-gcc/examples/dpdk-vhost_crypto

2, Bind QAT device and run the dpdk vhost sample in HOST side
usertools/dpdk-devbind.py --force --bind=3Dvfio-pci 0000:1a:01.0 0000:1c:01=
.0
0000:1e:01.0
x86_64-native-linuxapp-gcc/examples/dpdk-vhost_crypto  -l 1,2,3,4,5 -a
0000:1a:01.0 -a 0000:1c:01.0 -a 0000:1e:01.0 --vdev
crypto_scheduler_pmd_1,worker=3D0000:1a:01.0_qat_sym,worker=3D0000:1c:01.0_=
qat_sym,worker=3D0000:1e:01.0_qat_sym,mode=3Dround-robin,ordering=3Denable
--socket-mem 2048,0 -n 4  -- --config "(2,0,0),(3,0,0),(4,0,0),(5,0,0)=
"
--socket-file 2,/tmp/vm0_crypto0.sock=20=20=20=20=20=20=20
--socket-file=3D3,/tmp/vm0_crypto1.sock=20=20=20=20=20=20=20
--socket-file=3D4,/tmp/vm1_crypto0.sock=20=20=20=20=20=20=20
--socket-file=3D5,/tmp/vm1_crypto1.sock

3, Bind NIC PF to vfio-pci
usertools/dpdk-devbind.py --bind=3Dvfio-pci 0000:60:00.0 0000:60:00.1
0000:3b:00.0 0000:3b:00.1

4, Start VM0 by the qemu:
taskset -c 11,12,13,14 /usr/local/qemu-2.12.0/bin/qemu-system-x86_64  -name=
 vm0
-enable-kvm -pidfile /tmp/.vm0.pid -daemonize -monitor
unix:/tmp/vm0_monitor.sock,server,nowait -device e1000,netdev=3Dnttsip1  -n=
etdev
user,id=3Dnttsip1,hostfwd=3Dtcp:10.67.118.199:6410-:22 -device
vfio-pci,host=3D0000:3b:00.0,id=3Dpt_0 -device vfio-pci,host=3D0000:3b:00.1=
,id=3Dpt_1
-cpu host -smp 4 -m 4096 -object
memory-backend-file,id=3Dmem,size=3D4096M,mem-path=3D/dev/hugepages,share=
=3Don -numa
node,memdev=3Dmem -mem-prealloc -chardev
socket,path=3D/tmp/vm0_qga0.sock,server,nowait,id=3Dvm0_qga0 -device virtio=
-serial
-device virtserialport,chardev=3Dvm0_qga0,name=3Dorg.qemu.guest_agent.0 -vn=
c :1
-chardev socket,path=3D/tmp/vm0_crypto0.sock,id=3Dvm0_crypto0 -object
cryptodev-vhost-user,id=3Dcryptodev0,chardev=3Dvm0_crypto0 -device
virtio-crypto-pci,id=3Dcrypto0,cryptodev=3Dcryptodev0 -chardev
socket,path=3D/tmp/vm0_crypto1.sock,id=3Dvm0_crypto1 -object
cryptodev-vhost-user,id=3Dcryptodev1,chardev=3Dvm0_crypto1 -device
virtio-crypto-pci,id=3Dcrypto1,cryptodev=3Dcryptodev1 -drive
file=3D/root/VMs/ubuntu2004-0.img


[Actual Result]
VM logs:
root@dpdk-yaobing-purely147:~/dpdk# taskset -c 11,12,13,14
/usr/local/qemu-2.12.0/bin/qemu-system-x86_64  -name vm0 -enable-kvm -pidfi=
le
/tmp/.vm0.pid -daemonize -monitor unix:/tmp/vm0_monitor.sock,server,nowait
-device e1000,netdev=3Dnttsip1  -netdev
user,id=3Dnttsip1,hostfwd=3Dtcp:10.67.118.199:6010-:22 -device
vfio-pci,host=3D0000:3b:00.0,id=3Dpt_0 -device vfio-pci,host=3D0000:3b:00.1=
,id=3Dpt_1
-cpu host -smp 4 -m 4096 -object
memory-backend-file,id=3Dmem,size=3D4096M,mem-path=3D/dev/hugepages,share=
=3Don -numa
node,memdev=3Dmem -mem-prealloc -chardev
socket,path=3D/tmp/vm0_qga0.sock,server,nowait,id=3Dvm0_qga0 -device virtio=
-serial
-device virtserialport,chardev=3Dvm0_qga0,name=3Dorg.qemu.guest_agent.0 -vn=
c :1
-chardev socket,path=3D/tmp/vm0_crypto0.sock,id=3Dvm0_crypto0 -object
cryptodev-vhost-user,id=3Dcryptodev0,chardev=3Dvm0_crypto0 -device
virtio-crypto-pci,id=3Dcrypto0,cryptodev=3Dcryptodev0 -chardev
socket,path=3D/tmp/vm0_crypto1.sock,id=3Dvm0_crypto1 -object
cryptodev-vhost-user,id=3Dcryptodev1,chardev=3Dvm0_crypto1 -device
virtio-crypto-pci,id=3Dcrypto1,cryptodev=3Dcryptodev1 -drive
file=3D/root/VMs/ubuntu2004-0.img
qemu-system-x86_64: -object
cryptodev-vhost-user,id=3Dcryptodev0,chardev=3Dvm0_crypto0: Failed to read =
msg
header. Read 0 instead of 12. Original request 1.
qemu-system-x86_64: -object
cryptodev-vhost-user,id=3Dcryptodev0,chardev=3Dvm0_crypto0: failed to init
vhost_crypto for queue 0


DPDK VHOST sample HOST log:=20
root@dpdk-yaobing-purely147:~/dpdk#
x86_64-native-linuxapp-gcc/examples/dpdk-vhost_crypto  -l 1,2,3,4,5 -a
0000:1a:01.0 -a 0000:1c:01.0 -a 0000:1e:01.0 --vdev
crypto_scheduler_pmd_1,worker=3D0000:1a:01.0_qat_sym,worker=3D0000:1c:01.0_=
qat_sym,worker=3D0000:1e:01.0_qat_sym,mode=3Dround-robin,ordering=3Denable
--socket-mem 2048,0 -n 4  -- --config "(2,0,0),(3,0,0),(4,0,0),(5,0,0)=
"
--socket-file 2,/tmp/vm0_crypto0.sock=20=20=20=20=20=20=20
--socket-file=3D3,/tmp/vm0_crypto1.sock=20=20=20=20=20=20=20
--socket-file=3D4,/tmp/vm1_crypto0.sock=20=20=20=20=20=20=20
--socket-file=3D5,/tmp/vm1_crypto1.sock
EAL: Detected CPU lcores: 112
EAL: Detected NUMA nodes: 2
EAL: Detected static linkage of DPDK
EAL: Multi-process socket /var/run/dpdk/rte/mp_socket
EAL: Selected IOVA mode 'VA'
EAL: VFIO support initialized
EAL: Using IOMMU type 1 (Type 1)
EAL: Probe PCI driver: qat (8086:37c9) device: 0000:1a:01.0 (socket 0)
CRYPTODEV: Creating cryptodev 0000:1a:01.0_qat_sym
CRYPTODEV: Initialisation parameters - name: 0000:1a:01.0_qat_sym,socket id=
: 0,
max queue pairs: 0
CRYPTODEV: Creating cryptodev 0000:1a:01.0_qat_asym
CRYPTODEV: Initialisation parameters - name: 0000:1a:01.0_qat_asym,socket i=
d:
0, max queue pairs: 0
EAL: Probe PCI driver: qat (8086:37c9) device: 0000:1c:01.0 (socket 0)
CRYPTODEV: Creating cryptodev 0000:1c:01.0_qat_sym
CRYPTODEV: Initialisation parameters - name: 0000:1c:01.0_qat_sym,socket id=
: 0,
max queue pairs: 0
CRYPTODEV: Creating cryptodev 0000:1c:01.0_qat_asym
CRYPTODEV: Initialisation parameters - name: 0000:1c:01.0_qat_asym,socket i=
d:
0, max queue pairs: 0
EAL: Probe PCI driver: qat (8086:37c9) device: 0000:1e:01.0 (socket 0)
CRYPTODEV: Creating cryptodev 0000:1e:01.0_qat_sym
CRYPTODEV: Initialisation parameters - name: 0000:1e:01.0_qat_sym,socket id=
: 0,
max queue pairs: 0
CRYPTODEV: Creating cryptodev 0000:1e:01.0_qat_asym
CRYPTODEV: Initialisation parameters - name: 0000:1e:01.0_qat_asym,socket i=
d:
0, max queue pairs: 0
CRYPTODEV: Creating cryptodev crypto_scheduler_pmd_1
CRYPTODEV: Initialisation parameters - name: crypto_scheduler_pmd_1,socket =
id:
0, max queue pairs: 8
cryptodev_scheduler_create() line 140:   Scheduling mode =3D round-robin
cryptodev_scheduler_create() line 195:   Packet ordering =3D enable
USER1: Processing on Core 2 started
VHOST_CONFIG: (/tmp/vm0_crypto0.sock) logging feature is disabled in async =
copy
mode
VHOST_CONFIG: (/tmp/vm0_crypto0.sock) vhost-user server: socket created, fd=
: 49
VHOST_CONFIG: (/tmp/vm0_crypto0.sock) binding succeeded
CRYPTODEV: rte_cryptodev_start() line 1208: Device with dev_id=3D0 already
started
VHOST_CONFIG: (/tmp/vm0_crypto1.sock) logging feature is disabled in async =
copy
mode
VHOST_CONFIG: (/tmp/vm0_crypto1.sock) vhost-user server: socket created, fd=
: 53
USER1: Processing on Core 3 started
VHOST_CONFIG: (/tmp/vm0_crypto1.sock) binding succeeded
CRYPTODEV: rte_cryptodev_start() line 1208: Device with dev_id=3D0 already
started
VHOST_CONFIG: (/tmp/vm1_crypto0.sock) logging feature is disabled in async =
copy
mode
VHOST_CONFIG: (/tmp/vm1_crypto0.sock) vhost-user server: socket created, fd=
: 54
USER1: Processing on Core 4 started
VHOST_CONFIG: (/tmp/vm1_crypto0.sock) binding succeeded
CRYPTODEV: rte_cryptodev_start() line 1208: Device with dev_id=3D0 already
started
VHOST_CONFIG: (/tmp/vm1_crypto1.sock) logging feature is disabled in async =
copy
mode
VHOST_CONFIG: (/tmp/vm1_crypto1.sock) vhost-user server: socket created, fd=
: 55
USER1: Processing on Core 5 started
VHOST_CONFIG: (/tmp/vm1_crypto1.sock) binding succeeded
VHOST_CONFIG: (/tmp/vm0_crypto0.sock) new vhost user connection is 56
VHOST_CONFIG: (/tmp/vm0_crypto0.sock) new device, handle is 0
USER1: New Vhost-crypto Device /tmp/vm0_crypto0.sock, Device ID 0
Segmentation fault (core dumped)

[Regression]
Is this issue a regression: (Y/N) Y
Bad commit id: 6816d998b0 examples/vhost_crypto: fix user callbacks
commit 6816d998b04e26ca4468356e0a3c10daf65412eb
Author: Gowrishankar Muthukrishnan <gmuthukrishn@marvell.com>
Date:   Fri Feb 28 19:17:11 2025 +0530

    examples/vhost_crypto: fix user callbacks

    [ upstream commit f7cf44d49b1115238a87c5852db4b47290bfdc25 ]

    In order to handle new vhost user connection, use new_connection
    and destroy_connection callbacks.

    Fixes: f5188211c721 ("examples/vhost_crypto: add sample applicatio=
n")

    Signed-off-by: Gowrishankar Muthukrishnan <gmuthukrishn@marvell.com>
    Acked-by: Akhil Goyal <gak=
hil@marvell.com>
    Reviewed-by: Maxime Coquelin <maxime.coquelin@redhat.com>

You are receiving this mail because:
  • You are the assignee for the bug.
=20=20=20=20=20=20=20=20=20=20
= --17434059870.7d3b.250896--