From: Andrew Morton <akpm@linux-foundation.org>
To: Ian Kent <raven@themaw.net>
Cc: autofs mailing list <autofs@vger.kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Kernel Mailing List <linux-kernel@vger.kernel.org>,
Pan Bian <bianpan2016@163.com>
Subject: Re: [PATCH 3/3] autofs: add ignore mount option
Date: Tue, 29 Jan 2019 20:58:11 -0800 [thread overview]
Message-ID: <20190129205811.2bd83d93dbc05325a8c55954@linux-foundation.org> (raw)
In-Reply-To: <553f4a0daf09407371193d7d4782a759561a626a.camel@themaw.net>
On Wed, 30 Jan 2019 10:07:15 +0800 Ian Kent <raven@themaw.net> wrote:
> On Tue, 2019-01-29 at 17:16 -0800, Andrew Morton wrote:
> > On Sat, 12 Jan 2019 08:00:40 +0800 Ian Kent <raven@themaw.net> wrote:
> >
> > > Add an autofs file system mount option that can be used to provide
> > > a generic indicator to applications that the mount entry should be
> > > ignored when displaying mount information.
> >
> > What is the reason for adding this feature?
>
> In other OSes that provide autofs and that provide a mount list
> to user space based on the kernel mount list a no-op mount option
> ("ignore" is the one use on the most common OS) is allowed so that
> autofs file system users can optionally use it.
>
> The idea is that it be used by user space programs to exclude
> autofs mounts from consideration when reading the mounts list.
>
> Prior to the change to link /etc/mtab to /proc/self/mounts all
> I needed to do to achieve this was to use mount(2) and not update
> the mtab but now that no longer works.
>
> I know the symlinking happened a long time ago and I considered
> doing this then but, at the time I couldn't remember the commonly
> used option name and thought persuading the various utility
> maintainers would be too hard.
>
> But now I have a RHEL request to do this for compatibility for a
> widely used product so I want to go ahead with it and try and
> enlist the help of some utility package maintainers.
>
> Clearly, without the option nothing can be done so it's at least
> a start.
OK. I guess I can just paste the above into the changelog.
Also, Documentation/filesystems/autofs*.txt are owed an update?
next prev parent reply other threads:[~2019-01-30 4:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-12 0:00 [PATCH 1/3] autofs: drop dentry reference only when it is never used Ian Kent
2019-01-12 0:00 ` Ian Kent
2019-01-12 0:00 ` [PATCH 2/3] autofs - fix error return in autofs_fill_super() Ian Kent
2019-01-12 0:00 ` Ian Kent
2019-01-12 0:00 ` [PATCH 3/3] autofs: add ignore mount option Ian Kent
2019-01-12 0:00 ` Ian Kent
2019-01-30 1:16 ` Andrew Morton
2019-01-30 2:07 ` Ian Kent
2019-01-30 2:44 ` Ian Kent
2019-01-30 4:18 ` Al Viro
2019-01-30 4:45 ` Ian Kent
2019-01-30 4:58 ` Andrew Morton [this message]
2019-01-30 5:20 ` 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=20190129205811.2bd83d93dbc05325a8c55954@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=autofs@vger.kernel.org \
--cc=bianpan2016@163.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@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).