mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: ebiederm@xmission.com (Eric W. Biederman)
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] namespace filedescriptors
Date: Wed, 25 May 2011 14:00:49 -0700	[thread overview]
Message-ID: <m1pqn61on2.fsf@fess.ebiederm.org> (raw)


I have ripped out all of my work to wire up the syscalls and make that
work properly.

Please think about pulling:
git://git.kernel.org/pub/scm/linux/kernel/git/ebiederm/linux-2.6-nsfd.git

The code really cleans up working with namespaces.

The killer feature is probably going to be that it becomes trivial to
isolate a vpn connection into it's own network namespace, allowing
all of the weirdness that comes with vpn connections to be isolated.

If nothing happens with this until the next merge cycle I will
understand.

Eric W. Biederman (8):
      ns: proc files for namespace naming policy.
      ns: Introduce the setns syscall
      ns proc: Add support for the network namespace.
      ns proc: Add support for the uts namespace
      ns proc: Add support for the ipc namespace
      net: Allow setting the network namespace by fd
      ns: Declare sys_setns in syscalls.h
      ns proc: Return -ENOENT for a nonexistent /proc/self/ns/ entry.

Stephen Rothwell (1):
      net: fix get_net_ns_by_fd for !CONFIG_NET_NS


 fs/proc/Makefile            |    1 +
 fs/proc/base.c              |   20 ++---
 fs/proc/inode.c             |    7 ++
 fs/proc/internal.h          |   18 ++++
 fs/proc/namespaces.c        |  198 +++++++++++++++++++++++++++++++++++++++++++
 include/linux/if_link.h     |    1 +
 include/linux/proc_fs.h     |   21 +++++
 include/linux/syscalls.h    |    1 +
 include/net/net_namespace.h |    1 +
 ipc/namespace.c             |   37 ++++++++
 kernel/nsproxy.c            |   42 +++++++++
 kernel/utsname.c            |   39 +++++++++
 net/core/net_namespace.c    |   65 ++++++++++++++
 net/core/rtnetlink.c        |    5 +-
 14 files changed, 444 insertions(+), 12 deletions(-)

                 reply	other threads:[~2011-05-25 21:01 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=m1pqn61on2.fsf@fess.ebiederm.org \
    --to=ebiederm@xmission.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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

Powered by JetHome