linux-kernel - [patch -mm 0/7] pid namespace and namespace cleanups

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <20061017203004.555659000@localhost.localdomain>
Date:	Tue, 17 Oct 2006 22:30:04 +0200
From:	Cedric Le Goater <clg@...ibm.com>
To:	linux-kernel@...r.kernel.org
Cc:	Andrew Morton <akpm@...l.org>
Subject: [patch -mm 0/7] pid namespace and namespace cleanups

Hi,

The next serie contains some cleanups on namespaces that have been
lying in our container patchset for a while. The patches seem stable
enough and not too controversial to be good candidates for a -mm merge.

Here's a short summary of what they are doing :

* add a process_session() helper routine
* rename 'struct namespace' to 'struct mnt_namespace' 
* add pid namespace framework to nsproxy but without the unshare
  feature
* add a child_reaper per pid namespace
* add an id to nsproxy for a future syscall bind_ns

A next serie should follow soon, which depends on the above. 

* net namespace framework, empty object without any dependency on
  the layer
* unshare_ns syscall (unshare dedicated to namespaces with its own 
  flags) 
* bind_ns syscall enabling a process to switch nsproxy
* more cleanups for the pid namespace

Pending patches we are still working on :

* layer 3 net namespace providing a simple and fast isolation of
  a net interface
* full pid namespace, this is quite complex.

Thanks,

C.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/