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 DAC4D7CB0 for ; Thu, 31 Jan 2019 16:51:08 +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 47B027F6CB; Thu, 31 Jan 2019 15:51:08 +0000 (UTC) Received: from ktraynor.remote.csb (ovpn-117-200.ams2.redhat.com [10.36.117.200]) by smtp.corp.redhat.com (Postfix) with ESMTP id A54C25C26C; Thu, 31 Jan 2019 15:51:06 +0000 (UTC) From: Kevin Traynor To: Sachin Saxena Cc: Shreyansh Jain , dpdk stable Date: Thu, 31 Jan 2019 15:48:50 +0000 Message-Id: <20190131154901.5383-42-ktraynor@redhat.com> In-Reply-To: <20190131154901.5383-1-ktraynor@redhat.com> References: <20190131154901.5383-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.25]); Thu, 31 Jan 2019 15:51:08 +0000 (UTC) Subject: [dpdk-stable] patch 'bus/fslmc: fix to reset portal memory before use' 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: Thu, 31 Jan 2019 15:51:09 -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 02/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. Thanks. Kevin Traynor --- >>From 2f43b079d4591d9302997847b4fd1ed3e2e5a33a Mon Sep 17 00:00:00 2001 From: Sachin Saxena Date: Fri, 11 Jan 2019 12:24:04 +0000 Subject: [PATCH] bus/fslmc: fix to reset portal memory before use [ upstream commit 34cb995cde6136c75951b72be9867c2677f2a493 ] Uninitialized portal memory is causing unwanted issues. Fixes: 293c0ca94c36 ("bus/fslmc: support memory backed portals with QBMAN 5.0") Signed-off-by: Sachin Saxena Acked-by: Shreyansh Jain --- drivers/bus/fslmc/portal/dpaa2_hw_dpio.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/drivers/bus/fslmc/portal/dpaa2_hw_dpio.c b/drivers/bus/fslmc/portal/dpaa2_hw_dpio.c index ce0699842..4fc6efec5 100644 --- a/drivers/bus/fslmc/portal/dpaa2_hw_dpio.c +++ b/drivers/bus/fslmc/portal/dpaa2_hw_dpio.c @@ -370,4 +370,6 @@ dpaa2_create_dpio_device(int vdev_fd, dpio_dev->dpio = malloc(sizeof(struct fsl_mc_io)); + memset(dpio_dev->dpio, 0, sizeof(struct fsl_mc_io)); + if (!dpio_dev->dpio) { DPAA2_BUS_ERR("Memory allocation failure"); -- 2.19.0 --- Diff of the applied patch vs upstream commit (please double-check if non-empty: --- --- - 2019-01-31 15:44:06.721188756 +0000 +++ 0042-bus-fslmc-fix-to-reset-portal-memory-before-use.patch 2019-01-31 15:44:05.000000000 +0000 @@ -1,12 +1,13 @@ -From 34cb995cde6136c75951b72be9867c2677f2a493 Mon Sep 17 00:00:00 2001 +From 2f43b079d4591d9302997847b4fd1ed3e2e5a33a Mon Sep 17 00:00:00 2001 From: Sachin Saxena Date: Fri, 11 Jan 2019 12:24:04 +0000 Subject: [PATCH] bus/fslmc: fix to reset portal memory before use +[ upstream commit 34cb995cde6136c75951b72be9867c2677f2a493 ] + Uninitialized portal memory is causing unwanted issues. Fixes: 293c0ca94c36 ("bus/fslmc: support memory backed portals with QBMAN 5.0") -Cc: stable@dpdk.org Signed-off-by: Sachin Saxena Acked-by: Shreyansh Jain