From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: autofs4 hang in 2.6.37-rc1 Date: Mon, 15 Nov 2010 15:27:21 +0200 Message-ID: <4CE13539.1020106@redhat.com> References: <4CDFDC2B.6040205@redhat.com> <4CE00194.3070601@redhat.com> <1289785533.3248.18.camel@localhost> <201011150954.34289.arnd@arndb.de> <1289827341.3248.49.camel@localhost> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1289827341.3248.49.camel@localhost> Sender: linux-kernel-owner@vger.kernel.org List-ID: Content-Type: text/plain; charset="us-ascii"; format="flowed" To: Ian Kent Cc: Arnd Bergmann , autofs@linux.kernel.org, linux-kernel On 11/15/2010 03:22 PM, Ian Kent wrote: > > Ian, if you can prove that the lock is not needed, I think we shold > > just remove it. > > I don't think I can prove it but I will have a long look at the code. > I don't think it is needed and I expect I'll recommend it be removed. I've been running with the lock removed for a while with no ill effect. Of course it doesn't prove anything but at least it's a workaround for me. -- error compiling committee.c: too many arguments to function