DPDK patches and discussions
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 779] cryptodev_virtio_autotest crash
Date: Thu, 05 Aug 2021 11:30:58 +0000	[thread overview]
Message-ID: <bug-779-3@http.bugs.dpdk.org/> (raw)

https://bugs.dpdk.org/show_bug.cgi?id=779

            Bug ID: 779
           Summary: cryptodev_virtio_autotest crash
           Product: DPDK
           Version: 21.05
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: cryptodev
          Assignee: dev@dpdk.org
          Reporter: ciara.power@intel.com
  Target Milestone: ---

Created attachment 169
  --> https://bugs.dpdk.org/attachment.cgi?id=169&action=edit
Screenshot of where the autotest crashes. Unresponsive at this point.

When running the cryptodev_virtio_autotest, there is a seg fault and the app
crashes. This is seen when executing the ESN testsuite (see attached
screenshot).

From basic debugging myself, the problem seems to occur for the first ESN
testcase auth_encrypt_AES128CBC_HMAC_SHA1_esn_check() when trying to process
the crypto request.

-- 
You are receiving this mail because:
You are the assignee for the bug.

                 reply	other threads:[~2021-08-05 11:31 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-779-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;
as well as URLs for NNTP newsgroup(s).