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:	Thu, 29 Nov 2007 13:34:01 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Albert Cahalan <acahalan@...il.com>
Cc:	Guillaume Chazarain <guichaz@...oo.fr>, akpm@...ux-foundation.org,
	mm-commits@...r.kernel.org, ebiederm@...ssion.com, 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


* Albert Cahalan <acahalan@...il.com> wrote:

> > I am faced with incidents on an almost daily basis that show how 
> > much we kernel folks suck at defining new APIs. The only luck is 
> > that the set of system calls is fairly complete already - but in the 
> > rare case where we touch an API it's a catastrophy most of the time. 
> > With such an API track record we'd probably never survive as a 
> > user-space project.
> 
> Most of user-space is worse.

most of user-space is a 'leaf' node product, not infrastructure. The 
core infrastructure bits of userspace like glibc have a lot saner API 
practice than the kernel. (with a 10 times larger API exposure! There 
are 3000+ glibc APIs, contrast that with the few-hundred kernel APIs.)

> What shocks me is that people keep designing ABIs with structs that 
> contain holes. (data leaks, waste, portability trouble, etc.) This 
> happens in kernel ABIs all the time. It ought to be blocked by some 
> sort of build tool. (with a whitelist for old stuff)

what shocks me more is the wide gap between talk and deed ;-) Really, 
you had strong (and mostly unjust) words towards the containers stuff, 
with little constructive criticism - while what started out this 
discussion was your (in hindsight) shortsighted choice of mucking with 
/proc/self years ago. We all make mistakes but you seem to even be proud 
of it. If your goal is to bring Linux forward please become more 
constructive and cut out the insults towards others. (and you'll 
magically see less insults go in your general direction as well ;-)

	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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ