From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1762480AbXFAQum (ORCPT ); Fri, 1 Jun 2007 12:50:42 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1760941AbXFAQug (ORCPT ); Fri, 1 Jun 2007 12:50:36 -0400 Received: from nz-out-0506.google.com ([64.233.162.228]:45881 "EHLO nz-out-0506.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1758653AbXFAQuf (ORCPT ); Fri, 1 Jun 2007 12:50:35 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:date:from:to:cc:subject:message-id:references:mime-version:content-type:content-disposition:in-reply-to:user-agent; b=loJW5xtt9B5e/PRx0INEpXFMHkm+aVw2ct3Rf8+m76Cc9j5JzOQCIXrkoJLTKJkuqpNpkgYzWHK66/BQoKtC+27I82zqrNoX88dF37K/mpKxQLu1vcklgDbkanqMsEVzZ7ufpADRl38VbcPnIq53zr+HSKXJbhtf8xor/cUSb9Q= Date: Fri, 1 Jun 2007 20:49:26 +0400 From: Cyrill Gorcunov To: Eric Sandeen Cc: Andrew Morton , LKML , Jan Kara Subject: Re: [PATCH 2/2] Fix possible leakage of blocks in UDF Message-ID: <20070601164926.GA8398@cvg> References: <20070524165935.GB19709@duck.suse.cz> <20070524170554.GC19709@duck.suse.cz> <20070524203653.GA7693@duck.suse.cz> <465DF0B4.2050203@sandeen.net> <465DF91F.3010201@sandeen.net> <20070531174201.GB8392@cvg> <465F09E7.7000300@sandeen.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <465F09E7.7000300@sandeen.net> User-Agent: Mutt/1.5.13 (2006-08-11) Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org [Eric Sandeen - Thu, May 31, 2007 at 12:46:15PM -0500] | Cyrill Gorcunov wrote: | | >Eric, could you please try the following: | > | >1) declare the spinlock in the top of inode.c as | > | > DEFINE_SPINLOCK(udf_drop_lock); | > | >2) replace in udf_drop_inode() | > | > kernel_lock -> spin_lock(&udf_drop_lock); | > kernel_unlock -> spin_unlock(&udf_drop_lock); | > | >I'm not sure if it help but you may try ;) | > | > Cyrill | > | | I'm sure it'll avoid the deadlock but.... | | Any sense of what the BKL is actually trying to protect in this case? | | Is it really only trying to prevent concurrent prealloc-discarders, or | is there more? | | -Eric | Hi Eric, it seems BKL only trying to protect from concurrent discard_prealloc. Moreover, a lot of UDF code does call iput with BKL held, so the only solution I see is to add spinlocks to udf_drop_inode... I'm making patch soon. Any comments? Cyrill