From: David Howells <dhowells@redhat.com>
To: Ian Kent <raven@themaw.net>
Cc: Andi Kleen <ak@suse.de>,
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 15:05:07 +0100 [thread overview]
Message-ID: <23461.1161093907@redhat.com> (raw)
In-Reply-To: <1161093310.4937.37.camel@localhost>
Ian Kent <raven@themaw.net> wrote:
> 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 looks like my fixes for autofs4 need applying to autofs also.
David
next prev parent reply other threads:[~2006-10-17 14:05 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
2006-10-17 13:59 ` Ian Kent
2006-10-17 14:05 ` David Howells [this message]
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=23461.1161093907@redhat.com \
--to=dhowells@redhat.com \
--cc=ak@suse.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=raven@themaw.net \
/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