From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 8BA97A0C40 for ; Sat, 31 Jul 2021 11:37:17 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 5CE6440042; Sat, 31 Jul 2021 11:37:17 +0200 (CEST) Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) by mails.dpdk.org (Postfix) with ESMTP id 137ED40042; Sat, 31 Jul 2021 11:37:16 +0200 (CEST) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id ACD275C00B3; Sat, 31 Jul 2021 05:37:15 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute4.internal (MEProxy); Sat, 31 Jul 2021 05:37:15 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding:content-type; s=fm1; bh= PmPxKnvjFeX+2I29enlcJlA0JJJDh7RGO2/tHLUYUUg=; b=dIO43XasT9AMPdV1 oBdFPlZtUWvevxymw1Qczbox410QF6OMTSU+VYxBF+fNpRlSgO62Fh24+kkrA+w/ FLVCYaR7//T/+ep/kIRM2+wQhvmWyQVcQb3k5m93s4yOKwFI4SN9TY3IbCwN6m+a dLPaRPJvclpkTM9FfnpxNA0KlNfakYXrdWHGhJR4/hkkDG0ozqOGiWNKb7L+Yiq9 3S7HWb5Px45q6QFkAoPmgsQuQCoHz9QUjvRhj5PRyBui+2kRWuRK0YhaBtCFtVJ5 sOL8oOe8TxWl0w00DotjTEHbv2Yhl0afal18d5xiPZE3ijwLnSkpLsDReAkJrMuf GlZgMg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm3; bh=PmPxKnvjFeX+2I29enlcJlA0JJJDh7RGO2/tHLUYU Ug=; b=oM3996Lf21Im8sBmNqJHRpXWDOAGUXr2/y2vmOMW67NQNdAh6jjVUsD2z K4t0HOIaveJPYZ19K6DDW7fbcPwQv0SETBfLt7Ta940AVdM5NvrAvCp9a04lT6S/ xfTsrWfbhMFZOfR4vMiQGWLSZp7Je87Mh8w9PXNR/iuYo8UupuCh9IExXHPO74Xf 48jFJ0dSeW7icSvE7FgFdATdfqllTccYsPX/jIN6BA2aZ4f0csQDU87TcHuWcReF uTVfCcamCoLkNIfuVpjP6ELkIBq//LKHHL3zJzXORZ4JSn8AbBUmC+qYEF1NyOdQ 0YyFaJKIghNy3qycWEqcUlJ6EyAvQ== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvtddrheejgddujecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefhvffufffkjghfggfgtgesthfuredttddtvdenucfhrhhomhepvfhhohhmrghs ucfoohhnjhgrlhhonhcuoehthhhomhgrshesmhhonhhjrghlohhnrdhnvghtqeenucggtf frrghtthgvrhhnpedugefgvdefudfftdefgeelgffhueekgfffhfeujedtteeutdejueei iedvffegheenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhroh hmpehthhhomhgrshesmhhonhhjrghlohhnrdhnvght X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA; Sat, 31 Jul 2021 05:37:14 -0400 (EDT) From: Thomas Monjalon To: Michael Baum , Matan Azrad , Akhil Goyal Cc: "dev@dpdk.org" , "stable@dpdk.org" Date: Sat, 31 Jul 2021 11:37:13 +0200 Message-ID: <3033419.IPRROK5Ux9@thomas> In-Reply-To: References: <20210729065000.172793-1-michaelba@nvidia.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-stable] [dpdk-dev] [EXT] [PATCH] crypto/mlx5: fix driver probing error flow X-BeenThere: stable@dpdk.org X-Mailman-Version: 2.1.29 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" 30/07/2021 21:23, Akhil Goyal: > > In crypto driver probing, there are two validations after context > > allocation. > > > > When one of them fails, the context structure was not freed what caused > > a memory leak. > > > > Free it. > > > > Fixes: debb27ea3442 ("crypto/mlx5: create login object using DevX") > > Fixes: e8db4413cba5 ("crypto/mlx5: add keytag configuration") > > Cc: stable@dpdk.org > > > > Signed-off-by: Michael Baum > > Acked-by: Matan Azrad > > --- > Applied to dpdk-next-crypto > @Thomas Monjalon: I do not think title and patch description are inline. > You may fix it while pulling on main branch. New title: crypto/mlx5: fix leaks on probing failure