From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) by dpdk.org (Postfix) with ESMTP id 13ACE1B490 for ; Fri, 4 Jan 2019 14:26:51 +0100 (CET) Received: from smtp.corp.redhat.com (int-mx06.intmail.prod.int.phx2.redhat.com [10.5.11.16]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 6C06481127; Fri, 4 Jan 2019 13:26:50 +0000 (UTC) Received: from ktraynor.remote.csb (ovpn-117-13.ams2.redhat.com [10.36.117.13]) by smtp.corp.redhat.com (Postfix) with ESMTP id 5D8B05C233; Fri, 4 Jan 2019 13:26:48 +0000 (UTC) From: Kevin Traynor To: Arek Kusztal Cc: Fiona Trahe , Marko Kovacevic , dpdk stable Date: Fri, 4 Jan 2019 13:24:02 +0000 Message-Id: <20190104132455.15170-20-ktraynor@redhat.com> In-Reply-To: <20190104132455.15170-1-ktraynor@redhat.com> References: <20190104132455.15170-1-ktraynor@redhat.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Scanned-By: MIMEDefang 2.79 on 10.5.11.16 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.27]); Fri, 04 Jan 2019 13:26:50 +0000 (UTC) Subject: [dpdk-stable] patch 'crypto/qat: fix message for NULL algo setting unused counter' has been queued to LTS release 18.11.1 X-BeenThere: stable@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches for DPDK stable branches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Jan 2019 13:26:51 -0000 Hi, FYI, your patch has been queued to LTS release 18.11.1 Note it hasn't been pushed to http://dpdk.org/browse/dpdk-stable yet. It will be pushed if I get no objections before 01/11/19. So please shout if anyone has objections. Also note that after the patch there's a diff of the upstream commit vs the patch applied to the branch. This will indicate if there was any rebasing needed to apply to the stable branch. If there were code changes for rebasing (ie: not only metadata diffs), please double check that the rebase was correctly done. Thanks. Kevin Traynor --- >>From 0bf1868e47b7ebad67455b80a1725eb316af776c Mon Sep 17 00:00:00 2001 From: Arek Kusztal Date: Wed, 12 Dec 2018 20:59:04 +0100 Subject: [PATCH] crypto/qat: fix message for NULL algo setting unused counter [ upstream commit 4dc73ff7042a27602a738be4450a8bae39388c4f ] NULL algo algo does not to set counter flag so it should be zeroed. Fixes: db0e952a5c01 ("crypto/qat: add NULL capability") Signed-off-by: Arek Kusztal Acked-by: Fiona Trahe Acked-by: Marko Kovacevic --- drivers/crypto/qat/qat_sym_session.c | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/crypto/qat/qat_sym_session.c b/drivers/crypto/qat/qat_sym_session.c index d8cc70286..4d7ec01d4 100644 --- a/drivers/crypto/qat/qat_sym_session.c +++ b/drivers/crypto/qat/qat_sym_session.c @@ -1490,4 +1490,5 @@ int qat_sym_session_aead_create_cd_auth(struct qat_sym_session *cdesc, || cdesc->qat_hash_alg == ICP_QAT_HW_AUTH_ALGO_AES_XCBC_MAC || cdesc->qat_hash_alg == ICP_QAT_HW_AUTH_ALGO_AES_CBC_MAC + || cdesc->qat_hash_alg == ICP_QAT_HW_AUTH_ALGO_NULL ) hash->auth_counter.counter = 0; -- 2.19.0 --- Diff of the applied patch vs upstream commit (please double-check if non-empty: --- --- - 2019-01-04 13:23:07.931274408 +0000 +++ 0020-crypto-qat-fix-message-for-NULL-algo-setting-unused-.patch 2019-01-04 13:23:07.000000000 +0000 @@ -1,12 +1,13 @@ -From 4dc73ff7042a27602a738be4450a8bae39388c4f Mon Sep 17 00:00:00 2001 +From 0bf1868e47b7ebad67455b80a1725eb316af776c Mon Sep 17 00:00:00 2001 From: Arek Kusztal Date: Wed, 12 Dec 2018 20:59:04 +0100 Subject: [PATCH] crypto/qat: fix message for NULL algo setting unused counter +[ upstream commit 4dc73ff7042a27602a738be4450a8bae39388c4f ] + NULL algo algo does not to set counter flag so it should be zeroed. Fixes: db0e952a5c01 ("crypto/qat: add NULL capability") -Cc: stable@dpdk.org Signed-off-by: Arek Kusztal Acked-by: Fiona Trahe