From: Eric Sandeen <sandeen@sandeen.net>
To: Ian Kent <raven@themaw.net>, xfs <linux-xfs@vger.kernel.org>
Subject: Re: [PATCH] xfsprogs: ignore autofs mount table entries
Date: Thu, 8 Oct 2020 15:03:35 -0500 [thread overview]
Message-ID: <c3e211d0-48d7-c26f-b64d-b730fe997c4b@sandeen.net> (raw)
In-Reply-To: <160212194125.16851.17467120219710843339.stgit@mickey.themaw.net>
On 10/7/20 8:52 PM, Ian Kent wrote:
> Some of the xfsprogs utilities read the mount table via. getmntent(3).
>
> The mount table may contain (almost always these days since /etc/mtab is
> symlinked to /proc/self/mounts) autofs mount entries. During processing
> of the mount table entries statfs(2) can be called on mount point paths
> which will trigger an automount if those entries are direct or offset
> autofs mount triggers (indirect autofs mounts aren't affected).
>
> This can be a problem when there are a lot of autofs direct or offset
> mounts because real mounts will be triggered when statfs(2) is called.
> This can be particularly bad if the triggered mounts are NFS mounts and
> the server is unavailable leading to lengthy boot times or worse.
>
> Simply ignoring autofs mount entries during getmentent(3) traversals
> avoids the statfs() call that triggers these mounts. If there are
> automounted mounts (real mounts) at the time of reading the mount table
> these will still be seen in the list so they will be included if that
> actually matters to the reader.
>
> Recent glibc getmntent(3) can ignore autofs mounts but that requires the
> autofs user to configure autofs to use the "ignore" pseudo mount option
> for autofs mounts. But this isn't yet the autofs default (to prevent
> unexpected side effects) so that can't be used.
>
> The autofs direct and offset automount triggers are pseudo file system
> mounts and are more or less useless in terms on file system information
> so excluding them doesn't sacrifice useful file system information
> either.
>
> Consequently excluding autofs mounts shouldn't have any adverse side
> effects.
(usually this'd go below the "---")
> Changes since v1:
> - drop hunk from fsr/xfs_fsr.c.
>
> Signed-off-by: Ian Kent <raven@themaw.net>
> ---
> libfrog/linux.c | 2 ++
> libfrog/paths.c | 2 ++
> 2 files changed, 4 insertions(+)
>
> diff --git a/libfrog/linux.c b/libfrog/linux.c
> index 40a839d1..a45d99ab 100644
> --- a/libfrog/linux.c
> +++ b/libfrog/linux.c
> @@ -73,6 +73,8 @@ platform_check_mount(char *name, char *block, struct stat *s, int flags)
> * servers. So first, a simple check: does the "dev" start with "/" ?
> */
> while ((mnt = getmntent(f)) != NULL) {
> + if (!strcmp(mnt->mnt_type, "autofs"))
> + continue;
I may change the order of this test and the next, just so it continues to
align with the comment above. Shouldn't make any difference, right?
Otherwise:
Reviewed-by: Eric Sandeen <sandeen@redhat.com>
> if (mnt->mnt_fsname[0] != '/')
> continue;
> if (stat(mnt->mnt_dir, &mst) < 0)
> diff --git a/libfrog/paths.c b/libfrog/paths.c
> index 32737223..d6793764 100644
> --- a/libfrog/paths.c
> +++ b/libfrog/paths.c
> @@ -389,6 +389,8 @@ fs_table_initialise_mounts(
> return errno;
>
> while ((mnt = getmntent(mtp)) != NULL) {
> + if (!strcmp(mnt->mnt_type, "autofs"))
> + continue;
> if (!realpath(mnt->mnt_dir, rmnt_dir))
> continue;
> if (!realpath(mnt->mnt_fsname, rmnt_fsname))
>
>
next prev parent reply other threads:[~2020-10-08 20:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-08 1:52 [PATCH] xfsprogs: ignore autofs mount table entries Ian Kent
2020-10-08 1:54 ` Ian Kent
2020-10-08 20:03 ` Eric Sandeen [this message]
2020-10-09 0:49 ` Ian Kent
2020-10-15 8:25 ` Christoph Hellwig
-- strict thread matches above, loose matches on Subject: below --
2020-10-01 1:06 Ian Kent
2020-10-01 15:19 ` Darrick J. Wong
2020-10-02 2:55 ` Ian Kent
2020-10-01 21:22 ` Eric Sandeen
2020-10-02 2:27 ` Ian Kent
2020-10-02 4:40 ` Ian Kent
2020-10-08 20:02 ` Eric Sandeen
2020-10-09 0:55 ` Ian Kent
2020-10-02 15:15 ` Eric Sandeen
2020-10-07 4: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=c3e211d0-48d7-c26f-b64d-b730fe997c4b@sandeen.net \
--to=sandeen@sandeen.net \
--cc=linux-xfs@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;
as well as URLs for NNTP newsgroup(s).