From: Stephen Hemminger <stephen@networkplumber.org>
To: Hannes Frederic Sowa <hannes@stressinduktion.org>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH RFC iproute v1 1/4] afnetns: add iproute bits for afnetns
Date: Mon, 13 Mar 2017 08:10:06 -0700 [thread overview]
Message-ID: <20170313081006.78b3af9d@xeon-e3> (raw)
In-Reply-To: <20170312230138.5096-2-hannes@stressinduktion.org>
On Mon, 13 Mar 2017 00:01:35 +0100
Hannes Frederic Sowa <hannes@stressinduktion.org> wrote:
> diff --git a/include/namespace.h b/include/namespace.h
> index 51324b21ba0cd5..acecc8c1f0d2b8 100644
> --- a/include/namespace.h
> +++ b/include/namespace.h
> @@ -7,6 +7,7 @@
> #include <sys/syscall.h>
> #include <errno.h>
>
> +#define AFNETNS_RUN_DIR "/var/run/afnetns"
> #define NETNS_RUN_DIR "/var/run/netns"
> #define NETNS_ETC_DIR "/etc/netns"
>
> @@ -14,6 +15,10 @@
> #define CLONE_NEWNET 0x40000000 /* New network namespace (lo, device, names sockets, etc) */
> #endif
>
> +#ifndef CLONE_NEWAFNET
> +#define CLONE_NEWAFNET 0x00001000 /* Clone new afnet context */
> +#endif
> +
These bits really need to come from a kernel exported header.
next prev parent reply other threads:[~2017-03-13 15:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-12 23:01 [PATCH RFC iproute v1 0/4] afnetns: add support for afnetns Hannes Frederic Sowa
2017-03-12 23:01 ` [PATCH RFC iproute v1 1/4] afnetns: add iproute bits " Hannes Frederic Sowa
2017-03-13 15:10 ` Stephen Hemminger [this message]
2017-03-12 23:01 ` [PATCH RFC iproute v1 2/4] afnetns: support for ipv4/v6 address management Hannes Frederic Sowa
2017-03-12 23:01 ` [PATCH RFC iproute v1 3/4] afnetns: introduce lib/afnetns.c and a name cache Hannes Frederic Sowa
2017-03-12 23:01 ` [PATCH RFC iproute v1 4/4] afnetns: only show afnetns when show_details Hannes Frederic Sowa
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=20170313081006.78b3af9d@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=hannes@stressinduktion.org \
--cc=netdev@vger.kernel.org \
/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).