All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Matthew Mitchell <matthew@geodev.com>
Cc: autofs@linux.kernel.org
Subject: Re: "simultaneous" mounts causing weird behavior
Date: Tue, 04 Nov 2003 13:03:30 -0800	[thread overview]
Message-ID: <3FA81422.7070004@zytor.com> (raw)
In-Reply-To: <1067979370.2630.110.camel@aluminum>

Matthew Mitchell wrote:
> 
> Yes, I know that mount can do that now.  But automount is spawning the
> second mount before the first one completes, no?  Still seems like there
> should be some sort of mutual exclusion around the lookup_mount call.  I
> realize our workload is kind of funny in that the processes effectively
> _try_ to synchronize their automount request.  
> 

autofs 3 relied on the mutural exclusion inherent in mount(2).  When
this was changed, it introduced a race condition in autofs 3.  I have
asked to add a mount flag to override this new behaviour; I don't know
if one was ever introduced or added to mount(8).

> Has any of this changed in the 4.0-pre autofs?  I haven't read through
> its source yet.

autofs 4 uses a different mutural exclusion strategy, so I would *think*
it would not be affected.

	-hpa

  reply	other threads:[~2003-11-04 21:03 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-04 14:42 "simultaneous" mounts causing weird behavior Matthew Mitchell
2003-11-04 17:02 ` H. Peter Anvin
2003-11-04 20:56   ` Matthew Mitchell
2003-11-04 21:03     ` H. Peter Anvin [this message]
2003-11-05  0:51       ` Ian Kent
2003-11-05  0:49     ` Ian Kent
2003-11-05  0:46 ` Ian Kent
2003-11-05 16:57   ` Matthew Mitchell
2003-11-06  3:53     ` Ian Kent
2003-11-10 16:57       ` Matthew Mitchell
2003-11-11 13:33         ` [autofs] " Ian Kent
  -- strict thread matches above, loose matches on Subject: below --
2003-11-05 18:45 Ogden, Aaron A.

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=3FA81422.7070004@zytor.com \
    --to=hpa@zytor.com \
    --cc=autofs@linux.kernel.org \
    --cc=matthew@geodev.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.