linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ian Kent <raven@themaw.net>
To: Andi Kleen <ak@suse.de>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: BUG dcache.c:613 during autofs unmounting in 2.6.19rc2
Date: Tue, 17 Oct 2006 21:55:10 +0800	[thread overview]
Message-ID: <1161093310.4937.37.camel@localhost> (raw)
In-Reply-To: <200610171250.56522.ak@suse.de>

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



  reply	other threads:[~2006-10-17 13:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-16 14:58 BUG dcache.c:613 during autofs unmounting in 2.6.19rc2 Andi Kleen
2006-10-17  4:15 ` Ian Kent
2006-10-17 10:50   ` Andi Kleen
2006-10-17 13:55     ` Ian Kent [this message]
2006-10-17 13:59       ` Ian Kent
2006-10-17 14:05     ` David Howells
2006-10-17 16:18 ` AUTOFS3: Make sure all dentries refs are released before calling kill_anon_super() David Howells
2006-10-17 16:23   ` Ian Kent

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1161093310.4937.37.camel@localhost \
    --to=raven@themaw.net \
    --cc=ak@suse.de \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).