From: ebiederm@xmission.com (Eric W. Biederman)
To: Valdis.Kletnieks@vt.edu
Cc: linux-kernel@vger.kernel.org
Subject: Re: Recent changes to sysctl.h breaks glibc
Date: 19 May 2003 18:40:18 -0600 [thread overview]
Message-ID: <m1y9121mdp.fsf@frodo.biederman.org> (raw)
In-Reply-To: <200305200024.h4K0OnPc025466@turing-police.cc.vt.edu>
Valdis.Kletnieks@vt.edu writes:
> On Mon, 19 May 2003 17:55:06 MDT, Eric W. Biederman said:
> > If things must be maintained in concert it is a bug.
> >
> > With a fixed ABI people take advantage of new features as they
> > care for them. And in general to use new features requires new code.
>
> And if the kernel headers aren't maintained in concert with the kernel,
> new userspace code can't reach the new features.
>
> Therefor, by your definition, the current situation is a bug.
Yes, glibc uses kernel headers.
> Try compiling code that uses futexes on a system that has a kernel that
> supports them, but kernel-headers that haven't been upgraded to mention them.
> The kernel has the new code, the userspace has the new code, but gcc will
> turn around and whinge about the new code because there's a piece missing in
> between. So people *CANT* take advantage of the new features (unless they
> do something silly like drag their own foo.h file around where it can get
> out of sync with reality).
Or the build against a library that does that. There are not that
many libraries.
For a lot of system calls it is actively dangerous to assume dev_t ==
__kernel_dev_t. As glibc does some cute things in there.
Eric
next prev parent reply other threads:[~2003-05-20 0:31 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-18 20:21 Recent changes to sysctl.h breaks glibc Martin Schlemmer
2003-05-18 20:49 ` William Lee Irwin III
2003-05-18 21:12 ` Martin Schlemmer
2003-05-19 5:38 ` Christoph Hellwig
2003-05-19 10:43 ` Martin Schlemmer
2003-05-19 10:51 ` William Lee Irwin III
2003-05-19 11:14 ` Martin Schlemmer
2003-05-19 11:21 ` William Lee Irwin III
2003-05-19 11:33 ` Arjan van de Ven
2003-05-19 11:43 ` Christoph Hellwig
2003-05-19 12:52 ` Martin Schlemmer
2003-05-19 21:14 ` H. Peter Anvin
2003-05-19 22:44 ` William Lee Irwin III
2003-05-19 22:46 ` H. Peter Anvin
2003-05-19 22:56 ` William Lee Irwin III
2003-05-19 23:04 ` H. Peter Anvin
2003-05-20 6:06 ` Martin Schlemmer
2003-05-19 11:45 ` Christoph Hellwig
2003-05-19 12:56 ` Martin Schlemmer
2003-05-19 13:06 ` Christoph Hellwig
2003-05-19 16:56 ` Sam Ravnborg
2003-05-19 17:41 ` Linus Torvalds
2003-05-19 21:16 ` H. Peter Anvin
2003-05-19 22:18 ` Eric W. Biederman
2003-05-19 22:31 ` H. Peter Anvin
2003-05-19 22:20 ` Alan Cox
2003-05-19 23:28 ` Andries Brouwer
2003-05-20 10:35 ` Lionel Elie Mamane
2003-05-19 23:30 ` H. Peter Anvin
2003-05-19 23:05 ` Eric W. Biederman
2003-05-19 23:17 ` H. Peter Anvin
2003-05-19 23:55 ` Eric W. Biederman
2003-05-20 0:24 ` Valdis.Kletnieks
2003-05-20 0:40 ` Eric W. Biederman [this message]
2003-05-20 1:11 ` Valdis.Kletnieks
2003-05-20 22:10 ` H. Peter Anvin
2003-05-20 0:30 ` H. Peter Anvin
2003-05-20 0:54 ` David Woodhouse
2003-05-20 1:09 ` H. Peter Anvin
2003-05-20 1:42 ` Miles Bader
2003-05-20 4:12 ` H. Peter Anvin
2003-05-20 4:24 ` Miles Bader
2003-05-20 6:37 ` Eric W. Biederman
2003-05-20 7:24 ` H. Peter Anvin
2003-05-20 19:04 ` Eric W. Biederman
2003-05-20 7:44 ` Riley Williams
2003-05-20 14:01 ` Chris Friesen
2003-05-20 17:06 ` H. Peter Anvin
2003-05-21 4:39 ` Martin Schlemmer
2003-05-21 5:38 ` H. Peter Anvin
2003-05-21 5:58 ` Eric W. Biederman
2003-05-19 18:05 ` David Ford
2003-05-19 17:44 ` Alan Cox
2003-05-20 2:21 ` David Ford
2003-05-19 18:24 ` Christoph Hellwig
2003-05-19 17:59 ` David Ford
2003-05-19 18:06 ` Arjan van de Ven
2003-05-19 18:23 ` David Ford
2003-05-19 18:34 ` Arjan van de Ven
2003-05-19 19:43 ` Martin Schlemmer
2003-05-19 21:21 ` H. Peter Anvin
2003-05-19 21:35 ` Sam Ravnborg
2003-05-19 21:37 ` Arjan van de Ven
-- strict thread matches above, loose matches on Subject: below --
2003-05-19 19:54 Mudama, Eric
2003-05-19 20:36 ` Martin Schlemmer
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=m1y9121mdp.fsf@frodo.biederman.org \
--to=ebiederm@xmission.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.