From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dan Carpenter Subject: Re: [patch] iommu/vt-d: unlock on error in intel_iommu_load_translation_tables() Date: Tue, 2 Jun 2015 17:06:56 +0300 Message-ID: <20150602140656.GR11734@mwanda> References: <20150602100958.GC11247@mwanda> <20150602134505.GA20381@8bytes.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <20150602134505.GA20381@8bytes.org> Sender: kernel-janitors-owner@vger.kernel.org To: Joerg Roedel Cc: David Woodhouse , Li@mwanda, Zhen-Hua , iommu@lists.linux-foundation.org, kernel-janitors@vger.kernel.org List-Id: iommu@lists.linux-foundation.org On Tue, Jun 02, 2015 at 03:45:18PM +0200, Joerg Roedel wrote: > On Tue, Jun 02, 2015 at 01:09:58PM +0300, Dan Carpenter wrote: > > Smatch found some error paths that don't unlock. Also we can return > > -ENOMEM instead of -1 if we don't have an old root entry. > > > > Fixes: 5908f10af4b9 ('iommu/vt-d: datatypes and functions used for kdump') > > Signed-off-by: Dan Carpenter > > Applied, thanks. > > > Releasing the lock is good, but we might need to do other error handling > > as well. Presumably this function always succeeds anyway? It seems > > like it might be essential for booting. > > What do you mean by 'other error handling'? In error case a negative > value is returned and the caller checks that. I was just worried we should call __iommu_free_mapped_mem() or something. I don't know this code very well is what I'm saying... regards, dan carpenter