From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1750998AbWJQNzW (ORCPT ); Tue, 17 Oct 2006 09:55:22 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751006AbWJQNzW (ORCPT ); Tue, 17 Oct 2006 09:55:22 -0400 Received: from out1.smtp.messagingengine.com ([66.111.4.25]:23458 "EHLO out1.smtp.messagingengine.com") by vger.kernel.org with ESMTP id S1750998AbWJQNzV (ORCPT ); Tue, 17 Oct 2006 09:55:21 -0400 X-Sasl-enc: FrRZ8fPUMNxoaOVigxL9njZHdM7PgdBbbCDN+kr8u49y 1161093321 Subject: Re: BUG dcache.c:613 during autofs unmounting in 2.6.19rc2 From: Ian Kent To: Andi Kleen Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org In-Reply-To: <200610171250.56522.ak@suse.de> References: <200610161658.58288.ak@suse.de> <1161058535.11489.6.camel@localhost> <200610171250.56522.ak@suse.de> Content-Type: text/plain Date: Tue, 17 Oct 2006 21:55:10 +0800 Message-Id: <1161093310.4937.37.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.6.3 (2.6.3-1.fc5.5) Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Tue, 2006-10-17 at 12:50 +0200, Andi Kleen wrote: > On Tuesday 17 October 2006 06:15, Ian Kent wrote: > > On Mon, 2006-10-16 at 16:58 +0200, Andi Kleen wrote: > > > While unmounting autofs on shutdown my workstation got a dcache.c:613 BUG > > > with 2.6.19rc2. > > > > > > Only jpegs available unfortunately: > > > > > > http://one.firstfloor.org/~andi/autofs-oops1.jpg > > > http://one.firstfloor.org/~andi/autofs-oops2.jpg > > > > > > I think it was autofs3 instead of autofs4 - at least I got both compiled in. > > > The autofs user land was autofs-4.1.4 (-6 suse rpm) > > > > Don't think compiling both in is a good idea. > > They both register as "autofs" so you really should choose one and > > disable the other. > > > > For my part I have to recommend autofs4 (personally I'd like to see the > > autofs v3 module deprecated) and autofs4 is really needed if your using > > autofs version 4 or above. > > Well it always worked this way in earlier kernels and even if the > wrong module was suddenly used for some reason it shouldn't BUG. > So something is broken. True. There have been some changes in this area (David Howells made some changes which affected autofs4) and I'm not sure that the autofs module was reviewed. I didn't look closely at it at the time, I guess I should have. Sorry. It will take a while longer to work out if the autofs if open to the same issue resulting from Davids change. Ian