From mboxrd@z Thu Jan 1 00:00:00 1970 From: Al Viro Subject: Re: Linux 2.6.26-rc4 Date: Tue, 3 Jun 2008 18:50:53 +0100 Message-ID: <20080603175053.GF28946@ZenIV.linux.org.uk> References: <20080603105258.GV28946@ZenIV.linux.org.uk> <1212499623.3025.46.camel@raven.themaw.net> <1212509263.3025.66.camel@raven.themaw.net> <20080603164102.GB28946@ZenIV.linux.org.uk> <20080603165042.GC28946@ZenIV.linux.org.uk> <1212514104.3025.110.camel@raven.themaw.net> <20080603174125.GE28946@ZenIV.linux.org.uk> <1212514893.3025.123.camel@raven.themaw.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Linus Torvalds , Miklos Szeredi , jesper@krogh.cc, linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org To: Ian Kent Return-path: Content-Disposition: inline In-Reply-To: <1212514893.3025.123.camel@raven.themaw.net> Sender: linux-kernel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org On Wed, Jun 04, 2008 at 01:41:32AM +0800, Ian Kent wrote: > OK, I'll need to look at vfs_readdir(). > I thought vfs_readdir() would take the containing directory mutex as > does ->lookup(). vfs_readdir() takes i_mutex on directory it reads. I.e. on the victim in this case. lookup has i_mutex on directory it does lookup in, i.e. root in this case...