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, 8 Aug 2008 05:33:04 +0400
From:	Alexey Dobriyan <adobriyan@...il.com>
To:	david@...g.hm
Cc:	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: why are namespaces required?

On Thu, Aug 07, 2008 at 05:54:11PM -0700, david@...g.hm wrote:
> I am taking the time to create a minimal config for some new hardware with 
> 2.6.25.15 and noticed that CONFIG_NAMESPACES is forced to Yes unless 
> embeded is selected (at which time it becomes configurable)

For one thing, it doesn't directly control any code, CONFIG_PID_NS et al do.

> why are namespaces required?

They aren't required, just one more stupid config option.

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.

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