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
| ||
|
Date: Wed, 14 Nov 2007 14:26:19 +0300 From: Pavel Emelyanov <xemul@...nvz.org> To: Andrew Morton <akpm@...l.org> CC: Cedric Le Goater <clg@...ibm.com>, Serge Hallyn <serue@...ibm.com>, "Eric W. Biederman" <ebiederm@...ssion.com>, Linux Containers <containers@...ts.osdl.org>, Linux Kernel Mailing List <linux-kernel@...r.kernel.org> Subject: [PATCH 0/6] A config option to compile out some namespaces code (v4) Change against v3: rebased on 2.6.24-rc2-mm1 There were some questions like "do I need this on my cellphone" in reply to different namespaces patches. Indeed, the namespaces are not useful for most of the embedded systems, but the code creating and releasing them weights a lot. So I propose to add a config option which will help embedded people to reduce the vmlinux size. This option simply compiles out the namespaces cloning and releasing code *only*, but keeps all the other logic untouched (e.g. the notion of init_ns). Moreover, some of the namespaces might be not 100% ready by the time of Linux-2.6.xxx release (like user namespaces or pid namespaces are now). Since each namespace has its own option, which depends on the NAMESPACES, it can be mrked with "depends on EXPERIMENTAL/BROKEN/ANYTHING_ELSE" not to release the functionality that is not 100% ready yet. When someone tries to clone some namespace with their support turned off, he will receive an EINVAL error. This patchset can save more than 2KB from the vmlinux when turning the config option "NAMESPACES" to "n". Signed-off-by: Pavel Emelyanov <xemul@...nvz.org> - 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/
Powered by blists - more mailing lists