mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Randy.Dunlap" <rddunlap@osdl.org>
To: Rob Landley <rob@landley.net>
Cc: jgarzik@pobox.com, spam99@2thebatcave.com, linux-kernel@vger.kernel.org
Subject: Re: Using kernel headers that are not for the running kernel
Date: Mon, 21 Jun 2004 08:29:59 -0700	[thread overview]
Message-ID: <20040621082959.237645e7.rddunlap@osdl.org> (raw)
In-Reply-To: <200406201937.20057.rob@landley.net>

On Sun, 20 Jun 2004 19:37:20 -0500 Rob Landley wrote:

| On Sunday 20 June 2004 11:24, Jeff Garzik wrote:
| 
| > Kernel-internal headers and definitions should absolutely never be used
| > in userspace.
| 
| Hence the old #ifdef KERNEL stuff, or whatever the guard was...
| 
| My only confusion was that when the #ifdefs stopped being maintained (written 
| off as inherently unworkable because people just #defined KERNEL when they 
| shouldn't), no actual replacement was pursued.  Instead the attitude seemed 
| to be "this is glibc's problem", we're too busy trying to get 2.6 out to 
| actually worry about anybody using it.  And calling it glibc's problem 
| doesn't work for me, because want to use uclibc...
| 
| > H. Peter Anvin has suggested an include/abi which could be shared, and
| > this seem quite reasonable to me.  However, the monumental task of
| > separating kernel-internal definitions from ABI definitions still
| > remains.
| >
| > 	Jeff, really glad the linux-libc-headers guys started his effort
| 
| Mazur seems to be doing a really nice job of it so far.  I'm building a small 
| distro based on it and sending him bug reports when I can't get something to 
| compile.  I'm happy to use his work, but I'd rather it got integrated into 
| the kernel.
| 
| Now that it's mostly stabilized, it seems that the remaining work is mostly 
| auditing, integrating it in under the include/abi directory, and cleaning up 
| the normal kernel headers to include the abi stuff rather than defining their 
| own copies in the kernel internal headers.
| 
| If an abi directory was created, I'd be happy to submit a file or two at a 
| time into it (with the corresponding patches to remove the definitions from 
| the main include directory and #include abi/whatever instead...)
| 
| (Is there some effort _other_ than Mazur's work I should know about?  Or 
| something wrong with Mazur's cleanups?  Or somebody already doing this...?)

Yes, or sort of.  There's a linuxabi mailing list:

http://zytor.com/mailman/listinfo/linuxabi

and talk about doing a big push on this in early 2.7.
There are several interested parties, but I don't know how interested
the top-level maintainer is in accepting such patches.


--
~Randy

      reply	other threads:[~2004-06-21 15:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-17 23:28 Nick Bartos
2004-06-18  0:04 ` David Schwartz
2004-06-18 13:25   ` Krzysztof Halasa
2004-06-18  9:27 ` Jesper Juhl
2004-06-19 10:46 ` Rob Landley
2004-06-20 16:24   ` Jeff Garzik
2004-06-21  0:37     ` Rob Landley
2004-06-21 15:29       ` Randy.Dunlap [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=20040621082959.237645e7.rddunlap@osdl.org \
    --to=rddunlap@osdl.org \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rob@landley.net \
    --cc=spam99@2thebatcave.com \
    /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

all inboxes | Powered by JetHome®