From: Omar Sandoval <osandov@osandov.com>
To: Ian Kent <raven@themaw.net>
Cc: Andrew Morton <akpm@linux-foundation.org>,
autofs mailing list <autofs@vger.kernel.org>,
Kernel Mailing List <linux-kernel@vger.kernel.org>,
Al Viro <viro@ZenIV.linux.org.uk>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
"Eric W. Biederman" <ebiederm@xmission.com>,
kernel-team@fb.com
Subject: Re: [PATCH 3/4] autofs - make mountpoint checks namespace aware
Date: Fri, 16 Sep 2016 14:14:57 -0700 [thread overview]
Message-ID: <20160916211457.GA18830@vader.DHCP.thefacebook.com> (raw)
In-Reply-To: <20160914061445.24714.68331.stgit@pluto.themaw.net>
On Wed, Sep 14, 2016 at 02:14:45PM +0800, Ian Kent wrote:
> If an automount mount is clone(2)ed into a file system that is
> propagation private, when it later expires in the originating
> namespace subsequent calls to autofs ->d_automount() for that
> dentry in the original namespace will return ELOOP until the
> mount is manually umounted in the cloned namespace.
>
> In the same way, if an autofs mount is triggered by automount(8)
> running within a container the dentry will be seen as mounted in
> the root init namespace and calls to ->d_automount() in that namespace
> will return ELOOP until the mount is umounted within the container.
>
> Also, have_submounts() can return an incorect result when a mount
> exists in a namespace other than the one being checked.
>
> Signed-off-by: Ian Kent <raven@themaw.net>
> Cc: Al Viro <viro@ZenIV.linux.org.uk>
> Cc: Eric W. Biederman <ebiederm@xmission.com>
> Cc: Omar Sandoval <osandov@osandov.com>
I can confirm that this fixes my repro and hasn't caused any other
problems as far as I can tell.
Tested-by: Omar Sandoval <osandov@fb.com>
--
Omar
next prev parent reply other threads:[~2016-09-16 21:15 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-14 6:14 [PATCH 1/4] fs - make is_local_mountpoint() usable by others Ian Kent
2016-09-14 6:14 ` [PATCH 2/4] fs - add have_local_submounts() Ian Kent
2016-09-14 6:14 ` [PATCH 3/4] autofs - make mountpoint checks namespace aware Ian Kent
2016-09-14 17:28 ` Eric W. Biederman
2016-09-15 0:09 ` Ian Kent
2016-09-15 0:32 ` Omar Sandoval
2016-09-15 2:08 ` Eric W. Biederman
2016-09-15 4:12 ` Ian Kent
2016-09-15 8:19 ` Ian Kent
2016-09-16 0:47 ` Eric W. Biederman
2016-09-16 2:58 ` Ian Kent
2016-09-19 0:58 ` Ian Kent
2016-09-20 16:09 ` Eric W. Biederman
2016-09-15 1:03 ` Ian Kent
2016-09-16 21:14 ` Omar Sandoval [this message]
2016-09-17 20:10 ` Mateusz Guzik
2016-09-19 1:36 ` Ian Kent
2016-09-20 16:50 ` Eric W. Biederman
2016-09-20 22:44 ` Ian Kent
2016-09-20 23:00 ` Ian Kent
2016-09-22 1:33 ` Ian Kent
2016-09-22 15:43 ` Eric W. Biederman
2016-09-23 0:55 ` Ian Kent
2016-09-23 1:37 ` Eric W. Biederman
2016-09-23 4:26 ` Ian Kent
2016-09-23 12:00 ` Ian Kent
2016-09-28 10:18 ` Ian Kent
2016-09-23 19:15 ` Eric W. Biederman
2016-09-24 0:11 ` Ian Kent
2016-09-26 16:05 ` Eric W. Biederman
2016-09-27 1:52 ` Ian Kent
2016-09-27 13:14 ` Eric W. Biederman
2016-09-28 0:19 ` Ian Kent
2016-09-14 6:14 ` [PATCH 4/4] fs - remove unused have_submounts() function 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=20160916211457.GA18830@vader.DHCP.thefacebook.com \
--to=osandov@osandov.com \
--cc=akpm@linux-foundation.org \
--cc=autofs@vger.kernel.org \
--cc=ebiederm@xmission.com \
--cc=kernel-team@fb.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=raven@themaw.net \
--cc=viro@ZenIV.linux.org.uk \
/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
Powered by JetHome