From: Ingo Molnar <mingo@elte.hu>
To: Albert Cahalan <acahalan@gmail.com>
Cc: Guillaume Chazarain <guichaz@yahoo.fr>,
akpm@linux-foundation.org, mm-commits@vger.kernel.org,
ebiederm@xmission.com, oleg@tv-sign.ru, rjw@sisk.pl,
roland@redhat.com, xemul@openvz.org,
linux-kernel <linux-kernel@vger.kernel.org>,
Ulrich Drepper <drepper@redhat.com>
Subject: Re: + proc-fix-the-threaded-proc-self.patch added to -mm tree
Date: Thu, 29 Nov 2007 13:34:01 +0100 [thread overview]
Message-ID: <20071129123401.GA16609@elte.hu> (raw)
In-Reply-To: <787b0d920711281014i76f182b7xaba100247e4ee79a@mail.gmail.com>
* Albert Cahalan <acahalan@gmail.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
prev parent reply other threads:[~2007-11-29 12:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200711262339.lAQNdNrw029057@imap1.linux-foundation.org>
[not found] ` <20071128014901.4b303954@inria.fr>
2007-11-28 9:41 ` + proc-fix-the-threaded-proc-self.patch added to -mm tree Albert Cahalan
2007-11-28 10:46 ` Ingo Molnar
2007-11-28 11:31 ` Eric W. Biederman
2007-11-28 11:42 ` Eric W. Biederman
2007-11-28 17:47 ` Albert Cahalan
2007-11-29 21:40 ` Eric W. Biederman
2007-11-30 0:10 ` Ingo Molnar
2007-11-30 7:44 ` Albert Cahalan
2007-12-02 4:00 ` Eric W. Biederman
2007-11-28 18:14 ` Albert Cahalan
2007-11-29 12:34 ` Ingo Molnar [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20071129123401.GA16609@elte.hu \
--to=mingo@elte.hu \
--cc=acahalan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=drepper@redhat.com \
--cc=ebiederm@xmission.com \
--cc=guichaz@yahoo.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=mm-commits@vger.kernel.org \
--cc=oleg@tv-sign.ru \
--cc=rjw@sisk.pl \
--cc=roland@redhat.com \
--cc=xemul@openvz.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox