linux-kernel - Re: why are namespaces required?

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-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 08 Aug 2008 13:29:06 +0200
From:	Andi Kleen <andi@...stfloor.org>
To:	Alexey Dobriyan <adobriyan@...il.com>
Cc:	david@...g.hm, linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: why are namespaces required?

Alexey Dobriyan <adobriyan@...il.com> writes:
>
> And while we're at it, data from my usual config adding _NS options
> one-by-one.
>
> 	$ size vmlinux-000 vmlinux-uts-ns vmlinux-ipc-ns vmlinux-user-ns vmlinux-pid-ns 
> 	   text    data     bss     dec     hex filename
> 	2560804  217296  225280 3003380  2dd3f4 vmlinux-000
> 	2560948  217296  225280 3003524  2dd484 vmlinux-uts-ns	(+144)
> 	2561452  217296  225280 3004028  2dd67c vmlinux-ipc-ns	(+504)
> 	2561805  217296  225280 3004381  2dd7dd vmlinux-user-ns	(+353)
> 	2562819  217300  225280 3005399  2ddbd7 vmlinux-pid-ns	(+1018)
>
> What amazing .text savings we have here.

Fully agreed. Probably a lot of these CONFIG options should be just dropped.
They are quite user unfriendly with very little gain.

It seems like there is unbounded growth in different name space options
which also implies unbounded CONFIG growth. At least they should be all
consolidated into a single CONFIG.

-Andi

--
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/