All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Kent <raven@themaw.net>
To: Marcel De Boer <marcel.de_boer@nokia.com>, autofs@vger.kernel.org
Subject: Re: Near-simultaneous automount of multiple directories fails
Date: Fri, 08 Apr 2016 16:54:39 +0800	[thread overview]
Message-ID: <1460105679.2979.2.camel@themaw.net> (raw)
In-Reply-To: <alpine.LRH.2.11.1604080846130.26210@carrot.ant.ipd.priv>

On Fri, 2016-04-08 at 09:55 +0200, Marcel De Boer wrote:
> Hi!
> 
> I've already reported this on the CentOS bug tracker a while ago, but
> I 
> thought I'd report it here too.
> 
> https://bugs.centos.org/view.php?id=9835
> 
> Summarized (there's more information on the bug report): on one of our
> servers we initially saw that every few days one home directory became
> inaccessible. This happened to two different homedirectories (but only
> one 
> at a time) out of the couple hundred we have. We traced this to 
> simultaneously scheduled cron scripts running out of the affected 
> homedirectories, which caused both directories to be mounted nearly 
> simultaneously.
> 
> A test setup on a different machine (the primary description from the
> bug 
> report, as the server was not stock CentOS) also showed that if we had
> cron simultaneously mount four directories every 10 minutes, only half
> of 
> them would get mounted every time. On this machine an RPM rebuild of 
> autofs made the issue disappear, but it was much more persistent on
> the 
> server.
> 
> Eventually it seems that there is an issue in mount_mount() from 
> mount_nfs.c; to my untrained eye, it looks like it can get called 
> simultaneously from different threads, where they change shared 
> information, probably the 'hosts' or 'tmp' lists.

Whatever the problem is it isn't access to either of these two variables
or the lists they may represent.

They are both local variables of the mount_mount() function and so
cannot be accessed simultaneously by any other function.

Ian
--
To unsubscribe from this list: send the line "unsubscribe autofs" in

  reply	other threads:[~2016-04-08  8:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-08  7:55 Near-simultaneous automount of multiple directories fails Marcel De Boer
2016-04-08  8:54 ` Ian Kent [this message]
2016-04-08  9:46   ` Ian Kent
2016-04-08 11:37     ` Marcel De Boer
2016-04-10  2:34       ` 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=1460105679.2979.2.camel@themaw.net \
    --to=raven@themaw.net \
    --cc=autofs@vger.kernel.org \
    --cc=marcel.de_boer@nokia.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.