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 02:24:24 +1000 [thread overview]
Message-ID: <20030722022424.7480af8e.sfr@canb.auug.org.au> (raw)
In-Reply-To: <20030721142259.GA4315@ping.be>
On Mon, 21 Jul 2003 16:23:00 +0200 Kurt Roeckx <Q@ping.be> wrote:
>
> It seems the _timer part of siginfo is a little bit broken.
>
> It has:
> char _pad[sizeof( __ARCH_SI_UID_T) - sizeof(int)];
>
> Where __ARCH_SI_UID_T can be a short.
Except __ARCH_SI_UID_T is defined to be uid_t everywhere except sparc
where it is "unsigned int". In include/linux/types.h, uid_t is typdef'ed
to be __kernel_uid32_t (in the kernel), so __ARCH_SI_UID_T is always (at
least) 32 bits.
I was worried about that the first time I saw it as well.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
next prev parent reply other threads:[~2003-07-21 16:10 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 [this message]
2003-07-21 18:00 ` Kurt Roeckx
2003-07-21 23:51 ` Stephen Rothwell
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=20030722022424.7480af8e.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).