From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nick Piggin Subject: Re: [announce] vfs-scale git tree update Date: Thu, 13 Jan 2011 13:14:14 +1100 Message-ID: References: <20110107075831.GA14915@amd> <1294763679.2435.72.camel@doink> <1294768668.2435.177.camel@doink> <1294804776.2821.4.camel@perseus> <1294807279.2821.9.camel@perseus> <1294809426.2821.20.camel@perseus> <1294883313.2757.5.camel@perseus> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Cc: Linus Torvalds , aelder@sgi.com, Nick Piggin , Al Viro , linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org To: Ian Kent Return-path: In-Reply-To: <1294883313.2757.5.camel@perseus> Sender: linux-kernel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org On Thu, Jan 13, 2011 at 12:48 PM, Ian Kent wrote: > On Thu, 2011-01-13 at 12:01 +1100, Nick Piggin wrote: >> Hm, what are the concurrencies that you need protection from? > > Ha, I think I'm wrong about this, after looking more closely at this I'm > struggling to see why autofs4_lock is needed at all. Well you did send me a series of patches to remove it, but unfortunately that was just as you made some larger changes to autofs4 upstream and I wasn't able to keep them up to date. It would be much appreciated if you had time to take another look at all the locking and streamline it. Thanks, Nick