From: Jiri Benc <jbenc@redhat.com>
To: Vadim Kochan <vadim4j@gmail.com>
Cc: Brian Haley <brian.haley@hp.com>, netdev@vger.kernel.org
Subject: Re: [PATCH iproute2 3/3] ip netns: Delete all netns
Date: Fri, 9 Jan 2015 09:43:15 +0100 [thread overview]
Message-ID: <20150109094315.0c370971@griffin> (raw)
In-Reply-To: <20150107195517.GA4645@angus-think.lan>
On Wed, 7 Jan 2015 21:55:17 +0200, Vadim Kochan wrote:
> On Wed, Jan 07, 2015 at 02:40:51PM -0500, Brian Haley wrote:
> > Or you just trap the name "all" in the add case and don't allow it.
>
> So I think that do not allow to add netns "all" can be a solution, I'd
> like to hear from other people if it might be OK.
You can still add the name manually (there is software out there that
adds symlinks to /ver/run/netns), so nope, that's not a solution.
Generally, the only special names that could be used would be those
containing a letter not allowed in file name, i.e. \0 or '/'. Neither
of those sounds thrilling. I'm afraid the only working solution is a
new option.
Jiri
--
Jiri Benc
next prev parent reply other threads:[~2015-01-09 8:43 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-07 11:04 [PATCH iproute2 0/3] ip netns: Run over all netns Vadim Kochan
2015-01-07 11:04 ` [PATCH iproute2 1/3] lib: Exec func on each netns Vadim Kochan
2015-01-07 11:04 ` [PATCH iproute2 2/3] ip netns: Allow exec " Vadim Kochan
2015-01-07 11:04 ` [PATCH iproute2 3/3] ip netns: Delete all netns Vadim Kochan
2015-01-07 15:44 ` Brian Haley
2015-01-07 17:36 ` Vadim Kochan
2015-01-07 18:11 ` Vadim Kochan
2015-01-07 19:40 ` Brian Haley
2015-01-07 19:55 ` Vadim Kochan
2015-01-08 0:00 ` Cong Wang
2015-01-09 8:43 ` Jiri Benc [this message]
2015-01-09 9:54 ` Vadim Kochan
2015-01-09 14:24 ` Nicolas Dichtel
2015-01-08 0:04 ` [PATCH iproute2 0/3] ip netns: Run over " Cong Wang
2015-01-08 0:52 ` Vadim Kochan
2015-01-09 18:49 ` Cong Wang
2015-01-09 19:17 ` Vadim Kochan
2015-01-14 1:28 ` Stephen Hemminger
2015-01-14 16:13 ` Vadim Kochan
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=20150109094315.0c370971@griffin \
--to=jbenc@redhat.com \
--cc=brian.haley@hp.com \
--cc=netdev@vger.kernel.org \
--cc=vadim4j@gmail.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 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.