From: "Pathak, Pravin" <pravin.pathak@intel.com>
To: "users@dpdk.org" <users@dpdk.org>
Subject: [dpdk-users] DPDK 18.11 ASENI_MB segfault
Date: Thu, 7 Mar 2019 22:30:36 +0000 [thread overview]
Message-ID: <168A68C163D584429EF02A476D5274424DEDC71C@FMSMSX108.amr.corp.intel.com> (raw)
Hi -
I have multi-process application in which primary process initializes all crypto devices and sets up sessions. Secondary process uses the pre-initialized devices and sessions.
It was working fine till DPDK 18.05. When switched to DPDK 18.11, secondary process started giving seg fault on receive. Primary process can still send and receive packets to/from crypto devices.
When switched to use HW crypto (QAT) instead of software crypto, same application works fine on DPDK 18.11. Is the usage model correct? Anything changed in DPDK 18.11 which might explain this?
Regards
Pravin
GDB backtrace
Program terminated with signal SIGSEGV, Segmentation fault.
#0 post_process_mb_job (qp=0x7007df2d600, job=0x55b48daa6b00)
at /.../dpdk-18.11/drivers/crypto/aesni_mb/rte_aesni_mb_pmd.c:931
---Type <return> to continue, or q <return> to quit---
931 if (likely(op->status == RTE_CRYPTO_OP_STATUS_NOT_PROCESSED)) {
[Current thread is 1 (Thread 0x7f7e8b2f4c00 (LWP 39715))]
(gdb)
(gdb) p op
$1 = (struct rte_crypto_op *) 0x0
(gdb) p sess
$2 = <optimized out>
(gdb)
next reply other threads:[~2019-03-07 22:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-07 22:30 Pathak, Pravin [this message]
2019-03-13 10:13 ` Zhang, Roy Fan
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=168A68C163D584429EF02A476D5274424DEDC71C@FMSMSX108.amr.corp.intel.com \
--to=pravin.pathak@intel.com \
--cc=users@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;
as well as URLs for NNTP newsgroup(s).