linux-kernel - Re: + proc-fix-the-threaded-proc-self.patch added to -mm tree

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, 30 Nov 2007 01:10:29 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	"Eric W. Biederman" <ebiederm@...ssion.com>
Cc:	Albert Cahalan <acahalan@...il.com>,
	Guillaume Chazarain <guichaz@...oo.fr>,
	akpm@...ux-foundation.org, mm-commits@...r.kernel.org,
	oleg@...sign.ru, rjw@...k.pl, roland@...hat.com, xemul@...nvz.org,
	linux-kernel <linux-kernel@...r.kernel.org>,
	Ulrich Drepper <drepper@...hat.com>
Subject: Re: + proc-fix-the-threaded-proc-self.patch added to -mm tree


* Eric W. Biederman <ebiederm@...ssion.com> wrote:

> > You'll never run out of this sort of problem. Keeping Linux lean and 
> > simple would be far better.
> 
> Nah.  The control group stuff has all kinds of corner cases because it 
> is a new and untested API.  The namespace work after we get the code 
> cleanup up so it is maintainable and we can work with it is usually 
> just finding our globals through a pointer instead of from a static 
> variable.  Hardly a measurable cost on the best day.

yeah - anyone who claims that containers are 'fat' has likely not even 
looked at the code. Even maintainance-wise there's very visible positive 
effects: we do discover and properly map our "global resource" 
dependencies and abstract them. That increases cleanliness of our code 
and APIs all around.

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