From: Omar Sandoval <osandov@osandov.com>
To: Ian Kent <raven@themaw.net>
Cc: autofs@vger.kernel.org, linux-fsdevel@vger.kernel.org,
kernel-team@fb.com
Subject: Re: Autofs and mount namespaces
Date: Fri, 8 Apr 2016 13:21:23 -0700 [thread overview]
Message-ID: <20160408202123.GA12948@vader.dhcp.thefacebook.com> (raw)
In-Reply-To: <1460076663.3135.37.camel@themaw.net>
On Fri, Apr 08, 2016 at 08:51:03AM +0800, Ian Kent wrote:
> On Thu, 2016-04-07 at 11:19 -0700, Omar Sandoval wrote:
> > Hi, Ian,
> >
> > I wanted to bring up the issue of autofs and mount namespaces again,
> > which recently resurfaced in the thread here [1]. In that thread, you
> > mentioned that you had some patches to make autofs namespace-aware
> > that
> > you were holding on to. Do you think you could put those up so we can
> > all work out the issues you mentioned?
>
> I can but I haven't tested them at all.
>
> Possibly I could post them to the autofs list if you want to test and
> probably make changes to get them working.
>
> Would that be ok .... umm, I think I need to post the patch now anyway
> as it's the easiest way to demonstrate what I think is a better approach
> than the patch below ....
>
> I'm struggling to get back to work on this but I'm getting there and
> hope to return to it soon.
Thanks for taking a look. Your patch fixes the case I provided, and it
does look much better than my hack :) Like you said in your other email,
there are more cases, but this fix is a good start independent of those
cases. Were there any other patches that needed testing?
--
Omar
next prev parent reply other threads:[~2016-04-08 20:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-07 18:19 Autofs and mount namespaces Omar Sandoval
2016-04-07 19:08 ` kbuild test robot
2016-04-07 19:42 ` Omar Sandoval
2016-04-08 0:51 ` Ian Kent
2016-04-08 1:04 ` Ian Kent
2016-04-08 20:21 ` Omar Sandoval [this message]
2016-04-10 2:53 ` Ian Kent
2016-07-05 18:47 ` Omar Sandoval
2016-07-05 23:35 ` Ian Kent
2016-09-13 18:19 ` Omar Sandoval
2016-09-14 0:56 ` Ian Kent
2016-09-14 1:25 ` Omar Sandoval
2016-04-08 1:21 ` 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=20160408202123.GA12948@vader.dhcp.thefacebook.com \
--to=osandov@osandov.com \
--cc=autofs@vger.kernel.org \
--cc=kernel-team@fb.com \
--cc=linux-fsdevel@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).