From mboxrd@z Thu Jan 1 00:00:00 1970 From: Frederic Weisbecker Subject: Re: 2.6.35-rc4-git3: Reported regressions from 2.6.34 Date: Fri, 9 Jul 2010 04:56:30 +0200 Message-ID: <20100709025628.GK6405@nowhere> References: <-IGZ64uxA6G.A.P0H.bLmNMB@chimera> Mime-Version: 1.0 Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:received:date:from:to:cc :subject:message-id:references:mime-version:content-type :content-disposition:content-transfer-encoding:in-reply-to :user-agent; bh=0BD32tehe3M7yOR8Xxr1UGAjIaBjoe2m6WY9ovP2Jlw=; b=Au1A14Cj32BV2YEwHYTD2BIe1dv5Im8Vdf6ea1RZa7rxqHbP5WqANaJA6fQVlvnMLT DzJxb7aTg6VxqIjCOwU559edNmIXO3z/WHtPVg7yWqrgLOQUsslAUwas4vH1ZwCQDAje /AhXnw3qbKZP69I0Acugu+cEanxmBcUAr3xqo= Content-Disposition: inline In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org List-ID: Content-Type: text/plain; charset="iso-8859-1" To: Linus Torvalds Cc: "Rafael J. Wysocki" , Linux Kernel Mailing List , Maciej Rutecki , Andrew Morton , Kernel Testers List , Network Development , Linux ACPI , Linux PM List , Linux SCSI List , Linux Wireless List , DRI , Al Viro , Shawn Starr , Jesse Barnes , Dave Airlie , "David S. Miller" , Patrick McHardy , Jens Axboe On Thu, Jul 08, 2010 at 06:34:25PM -0700, Linus Torvalds wrote: > On Thu, Jul 8, 2010 at 4:33 PM, Rafael J. Wysocki wrote= : > > Bug-Entry =A0 =A0 =A0 : http://bugzilla.kernel.org/show_bug.cgi?id=3D= 16334 > > Subject =A0 =A0 =A0 =A0 : reiserfs locking (v2) > > Submitter =A0 =A0 =A0 : Sergey Senozhatsky > > Date =A0 =A0 =A0 =A0 =A0 =A0: 2010-07-02 9:34 (7 days old) > > Message-ID =A0 =A0 =A0: <20100702093451.GA3973@swordfish.minsk.epam= =2Ecom> > > References =A0 =A0 =A0: http://marc.info/?l=3Dlinux-kernel&m=3D1278= 06306303590&w=3D2 >=20 > Frederic? Al? I assume this is some late fallout from the BKL removal > ages ago.. It's the old filldir-vs-mmap crud, but normally it should > be impossible to trigger because the inode for a directory should > never be mmap'able, so we should never have the same i_mutex lock use= d > for both mmap and for filldir protection. >=20 > We saw some of that oddity long ago, I wonder if it's lockdep being > confused about some inodes. I think it has been there from the beginning. At least it was there bef= ore the reiserfs bkl removal in .32. Indeed the readdir <-> unmap/release inversion problem can not happen. But Al said that can happen between write and release. (Although I don'= t see where write takes the inode mutex). He also highlighted the fact that reiserfs refcounting based on i_count was totally broken. He has a fix the whole in the vfs tree, in the for-next branch on commi= t 6c2bdaf089a3876226893fab00dd83596c465ad2 "Fix reiserfs_file_release()" No more uses of the i_mutex on release after that, nor i_count, but a p= rivate openers refcount and a tailpack mutex per reiserfs inode.