From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by dpdk.space (Postfix) with ESMTP id 23E50A0679 for ; Tue, 30 Apr 2019 19:02:51 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 1A8835A6E; Tue, 30 Apr 2019 19:02:51 +0200 (CEST) Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) by dpdk.org (Postfix) with ESMTP id 257675A6E for ; Tue, 30 Apr 2019 19:02:50 +0200 (CEST) Received: from smtp.corp.redhat.com (int-mx04.intmail.prod.int.phx2.redhat.com [10.5.11.14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 8A5F0A3285; Tue, 30 Apr 2019 17:02:44 +0000 (UTC) Received: from rh.redhat.com (ovpn-117-211.ams2.redhat.com [10.36.117.211]) by smtp.corp.redhat.com (Postfix) with ESMTP id 998BD6D0B7; Tue, 30 Apr 2019 17:02:42 +0000 (UTC) From: Kevin Traynor To: Akhil Goyal Cc: Hemant Agrawal , dpdk stable Date: Tue, 30 Apr 2019 18:01:30 +0100 Message-Id: <20190430170133.2331-35-ktraynor@redhat.com> In-Reply-To: <20190430170133.2331-1-ktraynor@redhat.com> References: <20190430170133.2331-1-ktraynor@redhat.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Scanned-By: MIMEDefang 2.79 on 10.5.11.14 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.39]); Tue, 30 Apr 2019 17:02:49 +0000 (UTC) Subject: [dpdk-stable] patch 'crypto/dpaa: fix session destroy' has been queued to LTS release 18.11.2 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: , Errors-To: stable-bounces@dpdk.org Sender: "stable" Hi, FYI, your patch has been queued to LTS release 18.11.2 Note it hasn't been pushed to http://dpdk.org/browse/dpdk-stable yet. It will be pushed if I get no objections before 05/07/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. Queued patches can be viewed on a temporary branch at: https://github.com/kevintraynor/dpdk-stable-queue.git Thanks. Kevin Traynor --- >From 2fa3f31e26a3e3fe2fff2316bd6e7566d8049d34 Mon Sep 17 00:00:00 2001 From: Akhil Goyal Date: Wed, 17 Apr 2019 15:58:14 +0530 Subject: [PATCH] crypto/dpaa: fix session destroy [ upstream commit 261fb941858cfe3df7960fa43976436d71af13a2 ] Coverity issue: 336798 Fixes: 1f14d500bce1 ("crypto/dpaa_sec: support IPsec protocol offload") Fixes: 0a23d4b6f4c2 ("crypto/dpaa2_sec: support protocol offload IPsec") Signed-off-by: Akhil Goyal Acked-by: Hemant Agrawal --- drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c | 2 +- drivers/crypto/dpaa_sec/dpaa_sec.c | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c b/drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c index ec3111b29..a7973cc04 100644 --- a/drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c +++ b/drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c @@ -2865,5 +2865,5 @@ dpaa2_sec_security_session_destroy(void *dev __rte_unused, rte_free(s->cipher_key.data); rte_free(s->auth_key.data); - memset(sess, 0, sizeof(dpaa2_sec_session)); + memset(s, 0, sizeof(dpaa2_sec_session)); set_sec_session_private_data(sess, NULL); rte_mempool_put(sess_mp, sess_priv); diff --git a/drivers/crypto/dpaa_sec/dpaa_sec.c b/drivers/crypto/dpaa_sec/dpaa_sec.c index 8958fd06a..10201c58c 100644 --- a/drivers/crypto/dpaa_sec/dpaa_sec.c +++ b/drivers/crypto/dpaa_sec/dpaa_sec.c @@ -2167,5 +2167,5 @@ dpaa_sec_security_session_destroy(void *dev __rte_unused, rte_free(s->cipher_key.data); rte_free(s->auth_key.data); - memset(sess, 0, sizeof(dpaa_sec_session)); + memset(s, 0, sizeof(dpaa_sec_session)); set_sec_session_private_data(sess, NULL); rte_mempool_put(sess_mp, sess_priv); -- 2.20.1 --- Diff of the applied patch vs upstream commit (please double-check if non-empty: --- --- - 2019-04-30 17:58:15.458098754 +0100 +++ 0035-crypto-dpaa-fix-session-destroy.patch 2019-04-30 17:58:13.820139513 +0100 @@ -1 +1 @@ -From 261fb941858cfe3df7960fa43976436d71af13a2 Mon Sep 17 00:00:00 2001 +From 2fa3f31e26a3e3fe2fff2316bd6e7566d8049d34 Mon Sep 17 00:00:00 2001 @@ -5,0 +6,2 @@ +[ upstream commit 261fb941858cfe3df7960fa43976436d71af13a2 ] + @@ -9 +10,0 @@ -Cc: stable@dpdk.org @@ -19 +20 @@ -index 5b72b9ee4..0d273bb62 100644 +index ec3111b29..a7973cc04 100644 @@ -22 +23 @@ -@@ -2837,5 +2837,5 @@ dpaa2_sec_security_session_destroy(void *dev __rte_unused, +@@ -2865,5 +2865,5 @@ dpaa2_sec_security_session_destroy(void *dev __rte_unused, @@ -30 +31 @@ -index 8305f19a3..d9a7cd8a4 100644 +index 8958fd06a..10201c58c 100644 @@ -33 +34 @@ -@@ -2454,5 +2454,5 @@ dpaa_sec_security_session_destroy(void *dev __rte_unused, +@@ -2167,5 +2167,5 @@ dpaa_sec_security_session_destroy(void *dev __rte_unused,