All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Kent <raven@themaw.net>
To: Leonardo Chiquitto <leonardo.lists@gmail.com>
Cc: autofs@linux.kernel.org
Subject: Re: AutoFS creates unmountable directories when ghosting is enabled
Date: Wed, 09 Mar 2011 12:21:01 +0800	[thread overview]
Message-ID: <1299644461.3037.16.camel@perseus> (raw)
In-Reply-To: <1299644155.3037.15.camel@perseus>

On Wed, 2011-03-09 at 12:15 +0800, Ian Kent wrote:
> > 
> > Hello Ian,
> > 
> > I bisected this problem today and discovered that it appeared after the
> > following commit:
> > 
> > commit 08aafab4c1d0ab6227c80f8cd1086ae78556a370
> > Author: Ian Kent <raven@themaw.net>
> > Date:   Thu Sep 9 11:10:47 2010 +0800
> > 
> >     autofs-5.0.5 - fix direct map not updating on reread
> > 
> >     If the map type is explicitly specified for a map the map isn't
> >     properly updated when a re-read is requested. This is because
> >     the map stale flag is incorrectly cleared after after the lookup
> >     module reads the map instead of at the completion of the update
> >     procedure. The map stale flag should only be cleared if the map
> >     read fails for some reason, otherwise it is updated when the
> >     refresh is completed.
> > 
> > Does this ring a bell? If not, I'll see if I can debug it further tomorrow.
> 
> Not really.
> I'm still not sure your original patch deals with the problem fully.
> 
> Could you also have a look at and try (from kernel.org):
> autofs-5.0.5-fix-prune-cache-valid-check.patch

Although, looking again, maybe we need both patches.

> 
> Ian
> 

  reply	other threads:[~2011-03-09  4:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-10 19:10 AutoFS creates unmountable directories when ghosting is enabled Leonardo Chiquitto
2010-12-15  2:49 ` Ian Kent
2011-03-07  2:37   ` Leonardo Chiquitto
2011-03-09  4:15     ` Ian Kent
2011-03-09  4:21       ` Ian Kent [this message]
2011-03-09 14:09         ` Leonardo Chiquitto

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=1299644461.3037.16.camel@perseus \
    --to=raven@themaw.net \
    --cc=autofs@linux.kernel.org \
    --cc=leonardo.lists@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.