From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Kernel<->Userspace API issue
Date: 18 Apr 2003 01:42:29 -0700 [thread overview]
Message-ID: <b7odpl$g2l$1@cesium.transmeta.com> (raw)
In-Reply-To: 20030418092755.A25177@flint.arm.linux.org.uk
Followup to: <20030418092755.A25177@flint.arm.linux.org.uk>
By author: Russell King <rmk@arm.linux.org.uk>
In newsgroup: linux.dev.kernel
>
> A problem has recently been reported on the ARM lists regarding RT signal
> handling. It appears that there is an issue between glibc and the kernel,
> in that glibc has a different idea of the layout of structures passed
> from the kernel than the kernel itself.
>
> I think this is a case in point that our policy on "userspace must not
> include kernel headers" is completely wrong when it comes to user
> space interfaces. I believe we need is a clear set of defined user
> space interface headers which contain the definition of structures and
> numbers shared between user space and kernel space. ie, include/abi
> or some such.
>
> No, glibckernheaders (or whatever it is) is NOT the solution - that
> just creates yet another set of header files to potentially go out
> of sync.
>
This is basically the "ABI headers" issue I have been harping on about
for some time. It's a sizable job, though, and a matter of finding
someone to do it.
-hpa
--
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
Architectures needed: ia64 m68k mips64 ppc ppc64 s390 s390x sh v850 x86-64
next prev parent reply other threads:[~2003-04-18 8:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-18 8:27 Kernel<->Userspace API issue Russell King
2003-04-18 8:42 ` H. Peter Anvin [this message]
2003-04-18 11:19 ` Dr. David Alan Gilbert
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='b7odpl$g2l$1@cesium.transmeta.com' \
--to=hpa@zytor.com \
--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.