From: Tejun Heo <tj@kernel.org>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Andy Lutomirski <luto@amacapital.net>,
Alexei Starovoitov <alexei.starovoitov@gmail.com>,
David Ahern <dsa@cumulusnetworks.com>,
Andy Lutomirski <luto@kernel.org>,
Network Development <netdev@vger.kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Daniel Borkmann <daniel@iogearbox.net>,
Alexei Starovoitov <ast@kernel.org>
Subject: Re: [PATCH v2] bpf: Restrict cgroup bpf hooks to the init netns
Date: Sat, 28 Jan 2017 09:43:54 -0500 [thread overview]
Message-ID: <20170128144354.GA8721@mtj.duckdns.org> (raw)
In-Reply-To: <87wpdiejjg.fsf@xmission.com>
Hello, Eric.
On Thu, Jan 26, 2017 at 01:45:07PM +1300, Eric W. Biederman wrote:
> > Eric, does this sound okay to you? You're the authority on exposing
> > things like namespace ids to users.
>
> *Boggle* Things that run across all network namespaces break any kind
> of sense I have about thinking about them.
>
> Running across more than one network namespace by default seems very
> broken to me.
Can you explain why that is? Other namespaces don't behave this way.
For example, a PID namespace doesn't hide the processes at the system
level. It just gives additional nested names to the namespaced
processes and having objects visible at the system level is very
useful for monitoring and management. Are there inherent reasons why
network namespace should be very different from other namespaces in
this regard?
Thanks.
--
tejun
next prev parent reply other threads:[~2017-01-28 14:44 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-23 20:36 [PATCH v2] bpf: Restrict cgroup bpf hooks to the init netns Andy Lutomirski
2017-01-23 21:03 ` David Ahern
2017-01-23 21:49 ` Andy Lutomirski
2017-01-24 2:09 ` Alexei Starovoitov
2017-01-24 2:31 ` David Ahern
2017-01-24 2:39 ` Andy Lutomirski
2017-01-24 4:10 ` David Ahern
2017-01-24 4:16 ` Andy Lutomirski
2017-01-24 2:42 ` Andy Lutomirski
2017-01-24 3:13 ` Alexei Starovoitov
2017-01-24 3:37 ` Andy Lutomirski
2017-01-24 4:05 ` David Ahern
2017-01-24 4:32 ` Andy Lutomirski
2017-01-24 17:48 ` Alexei Starovoitov
2017-01-24 18:54 ` Andy Lutomirski
2017-01-24 20:29 ` David Ahern
2017-01-24 21:24 ` Andy Lutomirski
2017-01-24 21:34 ` David Ahern
2017-01-25 0:11 ` Alexei Starovoitov
2017-01-25 0:19 ` David Ahern
2017-01-25 20:28 ` Andy Lutomirski
2017-01-26 0:45 ` Eric W. Biederman
2017-01-28 14:43 ` Tejun Heo [this message]
2017-01-24 22:18 ` Tejun Heo
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=20170128144354.GA8721@mtj.duckdns.org \
--to=tj@kernel.org \
--cc=alexei.starovoitov@gmail.com \
--cc=ast@kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=dsa@cumulusnetworks.com \
--cc=ebiederm@xmission.com \
--cc=luto@amacapital.net \
--cc=luto@kernel.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).