From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Kurt Roeckx <Q@ping.be>
Cc: linux-kernel@vger.kernel.org
Subject: Re: siginfo pad problem.
Date: Tue, 22 Jul 2003 09:51:05 +1000 [thread overview]
Message-ID: <20030722095105.5ed2379a.sfr@canb.auug.org.au> (raw)
In-Reply-To: <20030721180032.GA26786@ping.be>
Hi Kurt,
On Mon, 21 Jul 2003 20:00:32 +0200 Kurt Roeckx <Q@ping.be> wrote:
>
> linux/types.h has:
> #ifdef __KERNEL__
> typedef __kernel_uid32_t uid_t;
> #else
> typedef __kernel_uid_t uid_t;
> #endif /* __KERNEL__ */
>
> And __kernel_uid_t is an "unsigned short"
Anywhere this should be used (i.e. only in the kernel), uid_t will be
__kernel_uid32_t. The change to this part of the siginfo_t structure has
not yet propogated to the glibc headers and when it does, it is up to the
glibc maintainers to make sure it matches what is used inside the kernel.
My extrapolation of your point leads me to ask why we even bother
with __KERNEL__ in the kernel's header files anymore since we keep
telling people that user mode programs should not use the kernel's
header files.
You are right that if a user mode program include the kernel's siginfo.h
(without defining __KERNEL__) it will not compile (on those architectures
where __kernel_uid_t is "unsigned short") but the answer I keep seeing
from this list is "Don't do that".
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
next prev parent reply other threads:[~2003-07-21 23:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-21 14:23 siginfo pad problem Kurt Roeckx
2003-07-21 16:24 ` Stephen Rothwell
2003-07-21 18:00 ` Kurt Roeckx
2003-07-21 23:51 ` Stephen Rothwell [this message]
2003-07-22 17:06 ` Kurt Roeckx
2003-07-22 17:14 ` Jamie Lokier
2003-07-22 17:19 ` Jakub Jelinek
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=20030722095105.5ed2379a.sfr@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=Q@ping.be \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).