From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from cuda.sgi.com (cuda3.sgi.com [192.48.176.15]) by oss.sgi.com (8.14.3/8.14.3/SuSE Linux 0.8) with ESMTP id q2CI2KjK120304 for ; Mon, 12 Mar 2012 13:02:21 -0500 Received: from bombadil.infradead.org (173-166-109-252-newengland.hfc.comcastbusiness.net [173.166.109.252]) by cuda.sgi.com with ESMTP id gB4DxkwAD02NZheU (version=TLSv1 cipher=AES256-SHA bits=256 verify=NO) for ; Mon, 12 Mar 2012 11:02:19 -0700 (PDT) Date: Mon, 12 Mar 2012 14:02:18 -0400 From: Christoph Hellwig Subject: Re: 3.2.9 and locking problem Message-ID: <20120312180218.GA22632@infradead.org> References: <201203092028.47177.arekm@maven.pl> <20120312005325.GX5091@dastard> <201203121443.59217.arekm@maven.pl> <20120312161425.GA23815@infradead.org> <4F5E371A.4000004@cape-horn-eng.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <4F5E371A.4000004@cape-horn-eng.com> List-Id: XFS Filesystem from SGI List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xfs-bounces@oss.sgi.com Errors-To: xfs-bounces@oss.sgi.com To: Richard Ems Cc: xfs@oss.sgi.com On Mon, Mar 12, 2012 at 06:49:14PM +0100, Richard Ems wrote: > Hi Christoph, > > On 03/12/2012 05:14 PM, Christoph Hellwig wrote: > > In the 3.2 version xfs_sync_flags does a double unlock of the ilock - > > change the last argument of xfs_trans_ijoin from XFS_ILOCK_EXCL to 0 > > will fix this. The 3.0 version doesn't have this bug. > > Is there already a fix or will there be one for 3.2.10 ? > > I am already using 3.2.x on 4 servers in production ... It's code added by the vserver patch that doesn't exist in mainline. _______________________________________________ xfs mailing list xfs@oss.sgi.com http://oss.sgi.com/mailman/listinfo/xfs