From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christoph Hellwig Subject: Re: [git pull] VFS - the first pile Date: Wed, 16 Mar 2011 09:18:00 -0400 Message-ID: <20110316131800.GA12175@infradead.org> References: <20110315213248.GL22723@ZenIV.linux.org.uk> <20110316061917.GA30195@dastard> <20110316065103.GP22723@ZenIV.linux.org.uk> <20110316072123.GR22723@ZenIV.linux.org.uk> <20110316130728.GB30866@infradead.org> <20110316131502.GS22723@ZenIV.linux.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Christoph Hellwig , Theodore Tso , Dave Chinner , Linus Torvalds , linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org To: Al Viro Return-path: Received: from bombadil.infradead.org ([18.85.46.34]:55138 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752733Ab1CPNSC (ORCPT ); Wed, 16 Mar 2011 09:18:02 -0400 Content-Disposition: inline In-Reply-To: <20110316131502.GS22723@ZenIV.linux.org.uk> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On Wed, Mar 16, 2011 at 01:15:02PM +0000, Al Viro wrote: > Yes. See patch upthread (or in for-linus). There are two parts in that > test; *both* would actually trigger the b0rkage in the last commit of > what got merged - the only reason why the first one (long chain) did not > was that the limit got fixed and -ELOOP was no longer triggered. Symlink > to itself did, of course, trigger it - complete with oops. Yes. I have a patch to increase the limit tested in 005 and it now passes fine.