From: dpdklab@iol.unh.edu
To: test-report@dpdk.org
Cc: dpdk-test-reports@iol.unh.edu
Subject: |WARNING| pw127438 [PATCH] [v3] crypto/qat: support to enable insecure algorithms
Date: Thu, 25 May 2023 11:58:12 -0700 (PDT) [thread overview]
Message-ID: <646fafc4.050a0220.356ea.576aSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-testing
Test-Status: WARNING
http://dpdk.org/patch/127438
_apply patch failure_
Submitter: Vikash Poddar <vikash.chandrax.poddar@intel.com>
Date: Thursday, May 25 2023 16:10:15
Applied on: CommitID:c9df59bcc9bec67783de98486879594e52bdc418
Apply patch set 127438 failed:
Checking patch app/test/test_cryptodev_asym.c...
Checking patch doc/guides/cryptodevs/qat.rst...
error: while searching for:
-a 03:01.1,qat_sym_cipher_crc_enable=1
Running QAT PMD with Intel IPSEC MB library for symmetric precomputes function
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
error: patch failed: doc/guides/cryptodevs/qat.rst:317
Checking patch drivers/common/qat/qat_device.c...
Hunk #1 succeeded at 365 (offset -6 lines).
Checking patch drivers/common/qat/qat_device.h...
Checking patch drivers/crypto/qat/dev/qat_crypto_pmd_gen2.c...
Checking patch drivers/crypto/qat/dev/qat_crypto_pmd_gen3.c...
Checking patch drivers/crypto/qat/dev/qat_crypto_pmd_gen4.c...
Checking patch drivers/crypto/qat/dev/qat_sym_pmd_gen1.c...
Checking patch drivers/crypto/qat/qat_asym.c...
Checking patch drivers/crypto/qat/qat_crypto.h...
Checking patch drivers/crypto/qat/qat_sym.c...
Hunk #2 succeeded at 282 (offset -4 lines).
Applied patch app/test/test_cryptodev_asym.c cleanly.
Applying patch doc/guides/cryptodevs/qat.rst with 1 reject...
Rejected hunk #1.
Applied patch drivers/common/qat/qat_device.c cleanly.
Applied patch drivers/common/qat/qat_device.h cleanly.
Applied patch drivers/crypto/qat/dev/qat_crypto_pmd_gen2.c cleanly.
Applied patch drivers/crypto/qat/dev/qat_crypto_pmd_gen3.c cleanly.
Applied patch drivers/crypto/qat/dev/qat_crypto_pmd_gen4.c cleanly.
Applied patch drivers/crypto/qat/dev/qat_sym_pmd_gen1.c cleanly.
Applied patch drivers/crypto/qat/qat_asym.c cleanly.
Applied patch drivers/crypto/qat/qat_crypto.h cleanly.
Applied patch drivers/crypto/qat/qat_sym.c cleanly.
hint: Use 'git am --show-current-patch' to see the failed patch
diff a/doc/guides/cryptodevs/qat.rst b/doc/guides/cryptodevs/qat.rst (rejected hunks)
@@ -317,6 +317,20 @@ To use this feature the user must set the devarg on process start as a device ad
-a 03:01.1,qat_sym_cipher_crc_enable=1
+Running QAT PMD with insecure crypto algorithms
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+A few insecure crypto algorithms are deprecated from QAT drivers. This needs to be reflected in DPDK QAT PMD.
+DPDK QAT PMD has by default disabled all the insecure crypto algorithms from Gen 1,2,3 and 4.
+A PMD parameter is used to enable the capability.
+
+- qat_legacy_capa
+
+To use this feature the user must set the parameter on process start as a device additional parameter::
+
+ -a b1:01.2,qat_legacy_capa=1
+
+
Running QAT PMD with Intel IPSEC MB library for symmetric precomputes function
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
https://lab.dpdk.org/results/dashboard/patchsets/26391/
UNH-IOL DPDK Community Lab
reply other threads:[~2023-05-25 18:58 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=646fafc4.050a0220.356ea.576aSMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=test-report@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).