From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Date: Wed, 28 Feb 2018 07:10:13 -0800 From: Jacob Pan To: Lu Baolu Cc: Joerg Roedel , iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org, Ashok Raj , "# v4 . 4+" , jacob.jun.pan@linux.intel.com Subject: Re: [PATCH 1/1] iommu/vt-d: Fix a potential memory leak Message-ID: <20180228071013.53e91c90@jacob-builder> In-Reply-To: <1519450947-9760-1-git-send-email-baolu.lu@linux.intel.com> References: <1519450947-9760-1-git-send-email-baolu.lu@linux.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: On Sat, 24 Feb 2018 13:42:27 +0800 Lu Baolu wrote: > A memory block was allocated in intel_svm_bind_mm() but never freed > in a failure path. This patch fixes this by free it to avoid memory > leakage. > looks good to me. Thanks, > Cc: Ashok Raj > Cc: Jacob Pan > Cc: # v4.4+ > Signed-off-by: Lu Baolu > --- > drivers/iommu/intel-svm.c | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/drivers/iommu/intel-svm.c b/drivers/iommu/intel-svm.c > index 35a408d..3d4b924 100644 > --- a/drivers/iommu/intel-svm.c > +++ b/drivers/iommu/intel-svm.c > @@ -396,6 +396,7 @@ int intel_svm_bind_mm(struct device *dev, int > *pasid, int flags, struct svm_dev_ pasid_max - 1, GFP_KERNEL); > if (ret < 0) { > kfree(svm); > + kfree(sdev); > goto out; > } > svm->pasid = ret; [Jacob Pan]