From: Andreas Schwab <schwab@suse.de>
To: Jamie Lokier <jamie@shareable.org>
Cc: Jakub Jelinek <jakub@redhat.com>,
linux-kernel@vger.kernel.org, linux-m68k@lists.linux-m68k.org
Subject: Re: sizeof (siginfo_t) problem
Date: Mon, 14 Jul 2003 17:02:26 +0200 [thread overview]
Message-ID: <jewueldud9.fsf@sykes.suse.de> (raw)
In-Reply-To: <20030714135540.GB26002@mail.jlokier.co.uk> (Jamie Lokier's message of "Mon, 14 Jul 2003 14:55:40 +0100")
Jamie Lokier <jamie@shareable.org> writes:
|> 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!
It should probably use the one from asm-generic as well. I could not
find anything that actually uses that field.
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux AG, Deutschherrnstr. 15-19, D-90429 Nürnberg
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2003-07-14 14:47 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 [this message]
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=jewueldud9.fsf@sykes.suse.de \
--to=schwab@suse.de \
--cc=jakub@redhat.com \
--cc=jamie@shareable.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.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).