From: Al Viro <viro@zeniv.linux.org.uk>
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>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH 3/3] autofs: add ignore mount option
Date: Wed, 30 Jan 2019 04:18:28 +0000 [thread overview]
Message-ID: <20190130041827.GI2217@ZenIV.linux.org.uk> (raw)
In-Reply-To: <804b86df6fd678147da816be038b11c87333b23f.camel@themaw.net>
On Wed, Jan 30, 2019 at 10:44:15AM +0800, Ian Kent wrote:
> Al,
>
> On a different note the above request also raised another
> question about statvfs(3) automount behaviour.
>
> In glibc statvfs(3) uses statfs(2) and translates the return
> to a statvfs structure.
>
> I wasn't aware but apparently statvfs(3) (and presumably statfs(2))
> doesn't trigger an automount on Solaris whereas we do. I think
> statfs() is probably the only exception to the convention that
> stat family system calls don't trigger an automount.
>
> So far I've said that this is a long standing behaviour in the
> Linux kernel and changing it could lead to unpleasant surprises
> for those that have come to expect this behaviour so such a change
> would not be well received.
>
> But I do need to ask your opinion, so what are your thoughts about
> changing this?
Probably should've done it that way, but I'm afraid it's much too
late by now...
next prev parent reply other threads:[~2019-01-30 4:18 UTC|newest]
Thread overview: 10+ 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 ` [PATCH 2/3] autofs - fix error return in autofs_fill_super() Ian Kent
2019-01-12 0:00 ` [PATCH 3/3] autofs: add ignore mount option 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 [this message]
2019-01-30 4:45 ` Ian Kent
2019-01-30 4:58 ` Andrew Morton
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=20190130041827.GI2217@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=akpm@linux-foundation.org \
--cc=autofs@vger.kernel.org \
--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 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.