From: Jamie Lokier <jamie@shareable.org>
To: Jakub Jelinek <jakub@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: sizeof (siginfo_t) problem
Date: Mon, 14 Jul 2003 14:55:40 +0100 [thread overview]
Message-ID: <20030714135540.GB26002@mail.jlokier.co.uk> (raw)
In-Reply-To: <20030714084000.J15481@devserv.devel.redhat.com>
Jakub Jelinek wrote:
> When siginfo_t was added, the intent obviously was that its size
> be 128 bytes on all arches.
>
> The kernel unfortunately does this right on sparc64 and alpha from 64-bit
> arches only; ia64, s390x, ppc64 etc. got it wrong.
That's not the only siginfo_t problem:
- Take a look at the placement of the _uid32 field on m68k.
It varies from sub-structure to sub-structure - yet it is
always written to the same offset by the kernel. Borken!
Other cleanups:
- SI_* codes on S390 are identical to the generic ones.
They can be removed from the S390 file.
- Comment in MIPS siginfo about IRIX compatibility is no
longer true; the layout was changed when uid32 added.
- __ARCH_SI_UID_T can be removed. Only Sparc sets it,
and to the same type as uid_t (unsigned int).
-- Jamie
next prev parent reply other threads:[~2003-07-14 13:44 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-14 12:40 sizeof (siginfo_t) problem Jakub Jelinek
2003-07-14 13:55 ` Jamie Lokier [this message]
2003-07-14 15:02 ` Andreas Schwab
2003-07-14 15:48 ` David Mosberger
2003-07-14 15:57 ` Jakub Jelinek
2003-07-14 16:52 ` Stephen Rothwell
2003-07-14 17:00 ` Jakub Jelinek
2003-07-14 17:11 ` Stephen Rothwell
2003-07-14 17:14 ` Jakub Jelinek
2003-07-14 17:25 ` Stephen Rothwell
2003-07-14 17:45 ` Jakub Jelinek
2003-07-19 18:32 ` Anton Blanchard
2003-07-21 0:08 ` Stephen Rothwell
2003-07-22 13:42 ` Russell King
2003-07-22 13:57 ` Stephen Rothwell
2003-07-14 18:31 Ulrich Weigand
2003-07-14 18:35 ` Jakub Jelinek
2003-07-14 18:52 Ulrich Weigand
2003-07-15 11:58 Martin Schwidefsky
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=20030714135540.GB26002@mail.jlokier.co.uk \
--to=jamie@shareable.org \
--cc=jakub@redhat.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.