From: Matteo Croce <mcroce@redhat.com>
To: David Howells <dhowells@redhat.com>
Cc: Nicolas Dichtel <nicolas.dichtel@6wind.com>,
Alexander Aring <aring@mojatatu.com>,
netdev <netdev@vger.kernel.org>,
linux-fsdevel@vger.kernel.org, kernel@mojatatu.com
Subject: Re: [RFC iproute2 1/1] ip: netns: add mounted state file for each netns
Date: Fri, 28 Jun 2019 19:06:45 +0200 [thread overview]
Message-ID: <CAGnkfhwe6p412q4sATwX=3ht4+NxKJDOFihRG=iwvXqWUtwgLQ@mail.gmail.com> (raw)
In-Reply-To: <18557.1561739215@warthog.procyon.org.uk>
On Fri, Jun 28, 2019 at 6:27 PM David Howells <dhowells@redhat.com> wrote:
>
> Nicolas Dichtel <nicolas.dichtel@6wind.com> wrote:
>
> > David Howells was working on a mount notification mechanism:
> > https://lwn.net/Articles/760714/
> > https://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git/log/?h=notifications
> >
> > I don't know what is the status of this series.
>
> It's still alive. I just posted a new version on it. I'm hoping, possibly
> futiley, to get it in in this merge window.
>
> David
Hi all,
this could cause a clash if I create a netns with name ending with .mounted.
$ sudo ip/ip netns add ns1.mounted
$ sudo ip/ip netns add ns1
Cannot create namespace file "/var/run/netns/ns1.mounted": File exists
Cannot remove namespace file "/var/run/netns/ns1.mounted": Device or
resource busy
If you want to go along this road, please either:
- disallow netns creation with names ending with .mounted
- or properly document it in the manpage
Regards,
--
Matteo Croce
per aspera ad upstream
next prev parent reply other threads:[~2019-06-28 17:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-26 19:03 [RFC iproute2 0/1] iproute2 netns mount race issue and solution? Alexander Aring
2019-06-26 19:03 ` [RFC iproute2 1/1] ip: netns: add mounted state file for each netns Alexander Aring
2019-06-27 12:08 ` Nicolas Dichtel
2019-06-28 16:26 ` David Howells
2019-06-28 17:06 ` Matteo Croce [this message]
2019-06-29 21:45 ` Matteo Croce
2019-07-01 12:34 ` Nicolas Dichtel
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='CAGnkfhwe6p412q4sATwX=3ht4+NxKJDOFihRG=iwvXqWUtwgLQ@mail.gmail.com' \
--to=mcroce@redhat.com \
--cc=aring@mojatatu.com \
--cc=dhowells@redhat.com \
--cc=kernel@mojatatu.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nicolas.dichtel@6wind.com \
/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).