From: Amir Goldstein <amir73il@gmail.com>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: Omar Sandoval <osandov@osandov.com>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Al Viro <viro@zeniv.linux.org.uk>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Jeff Layton <jlayton@poochiereds.net>
Subject: Re: [LSF/MM TOPIC] new mount(2) userspace api
Date: Thu, 6 Apr 2017 13:56:59 +0300 [thread overview]
Message-ID: <CAOQ4uxiSEKBndD1yiZxtacdUdeLsPBQuoKKsuXyC7uPJuE+KYQ@mail.gmail.com> (raw)
In-Reply-To: <CAJfpeguCm9bYsBtgXMhePdOQ6E+xbW1baG3U+o1h=5g661gg5A@mail.gmail.com>
On Fri, Jan 27, 2017 at 11:46 AM, Miklos Szeredi <miklos@szeredi.hu> wrote:
> On Fri, Jan 13, 2017 at 3:20 PM, Miklos Szeredi <miklos@szeredi.hu> wrote:
>> On Thu, Jan 12, 2017 at 6:56 PM, Omar Sandoval <osandov@osandov.com> wrote:
>>> On Wed, Jan 11, 2017 at 11:37:03AM +0100, Miklos Szeredi wrote:
>>>> General direction has been laid out by Al, but it would be good to
>>>> discuss the details.
>>>>
>>>> I plan to work on this after overlayfs is "done".
>>>>
>>>> Thanks,
>>>> Miklos
>>>
>>> Hi, Miklos,
>>>
>>> What's the background on this? Is there a mailing list thread?
>>
>> http://marc.info/?t=138677271200004&r=1&w=2
>>
>> https://lwn.net/Articles/609376/
>
> Found one more:
>
> https://lists.linuxfoundation.org/pipermail/ksummit-discuss/2014-August/001199.html
Miklos,
WRT the suggestion to use a netlink socket that was made in LSF, be aware that
netlink sockets are per network-ns and mounts as you know are per mount-ns.
That may be a problem when setting up a mount from non root network-ns
or maybe not? - I am not sure.
Amir.
next prev parent reply other threads:[~2017-04-06 10:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-11 10:37 [LSF/MM TOPIC] new mount(2) userspace api Miklos Szeredi
2017-01-12 17:56 ` Omar Sandoval
2017-01-13 14:20 ` Miklos Szeredi
2017-01-27 9:46 ` Miklos Szeredi
2017-04-06 10:56 ` Amir Goldstein [this message]
2017-04-06 17:46 ` Eric W. Biederman
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=CAOQ4uxiSEKBndD1yiZxtacdUdeLsPBQuoKKsuXyC7uPJuE+KYQ@mail.gmail.com \
--to=amir73il@gmail.com \
--cc=ebiederm@xmission.com \
--cc=jlayton@poochiereds.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=osandov@osandov.com \
--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;
as well as URLs for NNTP newsgroup(s).