From: Mike Marion <mmarion@qualcomm.com>
To: Ian Kent <raven@themaw.net>
Cc: NeilBrown <neilb@suse.com>, Al Viro <viro@ZenIV.linux.org.uk>,
Colin Walters <walters@redhat.com>,
Ondrej Holy <oholy@redhat.com>,
autofs mailing list <autofs@vger.kernel.org>,
Kernel Mailing List <linux-kernel@vger.kernel.org>,
David Howells <dhowells@redhat.com>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: [PATCH 3/3] autofs - fix AT_NO_AUTOMOUNT not being honored
Date: Mon, 27 Nov 2017 16:01:53 +0000 [thread overview]
Message-ID: <20171127160147.GA27613@qualcomm.com> (raw)
In-Reply-To: <864efc64-c430-a862-3e98-fe5ce2535329@themaw.net>
On Thu, Nov 23, 2017 at 08:36:49AM +0800, Ian Kent wrote:
> And with the move of userspace to use /proc based mount tables (one
> example being the symlink of /etc/mtab into /proc) even modest sized
> direct mount maps will be a problem with every entry getting mounted.
>
> Systems will cope with this fine but larger systems not so much.
Yes.. we've run into some big issues due to the change of /etc/mtab from
a file to a symlink to /proc/self/mounts. Most have been worked around
thus far (mostly due to Suse coming up with patches) but still have a
few annoying ones.
--
Mike Marion-Unix SysAdmin/Sr. Staff IT Engineer-http://www.qualcomm.com--
To unsubscribe from this list: send the line "unsubscribe autofs" in
WARNING: multiple messages have this Message-ID (diff)
From: Mike Marion <mmarion@qualcomm.com>
To: Ian Kent <raven@themaw.net>
Cc: NeilBrown <neilb@suse.com>, Al Viro <viro@ZenIV.linux.org.uk>,
"Colin Walters" <walters@redhat.com>,
Ondrej Holy <oholy@redhat.com>,
"autofs mailing list" <autofs@vger.kernel.org>,
Kernel Mailing List <linux-kernel@vger.kernel.org>,
David Howells <dhowells@redhat.com>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: [PATCH 3/3] autofs - fix AT_NO_AUTOMOUNT not being honored
Date: Mon, 27 Nov 2017 16:01:53 +0000 [thread overview]
Message-ID: <20171127160147.GA27613@qualcomm.com> (raw)
In-Reply-To: <864efc64-c430-a862-3e98-fe5ce2535329@themaw.net>
On Thu, Nov 23, 2017 at 08:36:49AM +0800, Ian Kent wrote:
> And with the move of userspace to use /proc based mount tables (one
> example being the symlink of /etc/mtab into /proc) even modest sized
> direct mount maps will be a problem with every entry getting mounted.
>
> Systems will cope with this fine but larger systems not so much.
Yes.. we've run into some big issues due to the change of /etc/mtab from
a file to a symlink to /proc/self/mounts. Most have been worked around
thus far (mostly due to Suse coming up with patches) but still have a
few annoying ones.
--
Mike Marion-Unix SysAdmin/Sr. Staff IT Engineer-http://www.qualcomm.com
next prev parent reply other threads:[~2017-11-27 16:01 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-10 4:18 [PATCH 1/3] autofs - make disc device user accessible Ian Kent
2017-05-10 4:18 ` Ian Kent
2017-05-10 4:18 ` [PATCH 2/3] autofs - make dev ioctl version and ismountpoint " Ian Kent
2017-05-10 4:18 ` Ian Kent
2017-05-10 4:18 ` [PATCH 3/3] autofs - fix AT_NO_AUTOMOUNT not being honored Ian Kent
2017-05-12 12:49 ` Colin Walters
2017-05-12 12:49 ` Colin Walters
2017-11-21 1:53 ` NeilBrown
2017-11-22 4:28 ` Ian Kent
2017-11-22 4:28 ` Ian Kent
2017-11-23 0:36 ` Ian Kent
2017-11-23 2:21 ` NeilBrown
2017-11-23 2:46 ` Ian Kent
2017-11-23 3:04 ` Ian Kent
2017-11-23 3:04 ` Ian Kent
2017-11-23 4:49 ` NeilBrown
2017-11-23 6:34 ` Ian Kent
2017-11-27 16:01 ` Mike Marion [this message]
2017-11-27 16:01 ` Mike Marion
2017-11-27 23:43 ` Ian Kent
2017-11-28 0:29 ` Mike Marion
2017-11-28 0:29 ` Mike Marion
2017-11-29 1:17 ` NeilBrown
2017-11-29 2:13 ` Mike Marion
2017-11-29 2:13 ` Mike Marion
2017-11-29 2:28 ` Ian Kent
2017-11-29 2:48 ` NeilBrown
2017-11-29 3:14 ` Ian Kent
2017-11-29 3:14 ` Ian Kent
2017-11-29 2:56 ` Ian Kent
2017-11-29 2:56 ` Ian Kent
2017-11-29 3:45 ` NeilBrown
2017-11-29 6:00 ` Ian Kent
2017-11-29 6:00 ` Ian Kent
2017-11-29 7:39 ` NeilBrown
2017-11-30 0:00 ` Ian Kent
2017-11-29 16:51 ` Mike Marion
2017-11-29 16:51 ` Mike Marion
2017-11-23 0:47 ` NeilBrown
2017-11-23 1:43 ` Ian Kent
2017-11-23 1:43 ` Ian Kent
2017-11-23 2:26 ` Ian Kent
2017-11-23 3:04 ` NeilBrown
2017-11-23 3:41 ` 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=20171127160147.GA27613@qualcomm.com \
--to=mmarion@qualcomm.com \
--cc=autofs@vger.kernel.org \
--cc=dhowells@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@suse.com \
--cc=oholy@redhat.com \
--cc=raven@themaw.net \
--cc=viro@ZenIV.linux.org.uk \
--cc=walters@redhat.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.