From: Jakub Jelinek <jakub@redhat.com>
To: davidm@hpl.hp.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: sizeof (siginfo_t) problem
Date: Mon, 14 Jul 2003 11:57:29 -0400 [thread overview]
Message-ID: <20030714115729.K15481@devserv.devel.redhat.com> (raw)
In-Reply-To: <16146.53424.388683.213654@napali.hpl.hp.com>; from davidm@napali.hpl.hp.com on Mon, Jul 14, 2003 at 08:48:00AM -0700
On Mon, Jul 14, 2003 at 08:48:00AM -0700, David Mosberger wrote:
> Jakub> The kernel unfortunately does this right on sparc64 and alpha
> Jakub> from 64-bit arches only; ia64, s390x, ppc64 etc. got it
> Jakub> wrong.
>
> The ia64 kernel defines in asm-ia64/siginfo.h:
>
> #define SI_PAD_SIZE ((SI_MAX_SIZE/sizeof(int)) - 4)
>
> typedef struct siginfo {
> int si_signo;
> int si_errno;
> int si_code;
> int __pad0;
>
> What's wrong with that?
Oops, sorry, you're right, dunno where I was looking.
So, the bug seems to exist on s390x, amd64, maybe parisc64 if such thing
exists.
Jakub
next prev parent reply other threads:[~2003-07-14 15:42 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
2003-07-14 15:02 ` Andreas Schwab
2003-07-14 15:48 ` David Mosberger
2003-07-14 15:57 ` Jakub Jelinek [this message]
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
-- strict thread matches above, loose matches on Subject: below --
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=20030714115729.K15481@devserv.devel.redhat.com \
--to=jakub@redhat.com \
--cc=davidm@hpl.hp.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox