From: Ralf Baechle <ralf@linux-mips.org>
To: Vivien Chappelier <vivienc@nerim.net>
Cc: Andrew Clausen <clausen@melbourne.sgi.com>, linux-mips@linux-mips.org
Subject: Re: sigset_t32 broken?
Date: Fri, 24 Jan 2003 02:48:54 +0100 [thread overview]
Message-ID: <20030124024854.B9031@linux-mips.org> (raw)
In-Reply-To: <Pine.LNX.4.21.0301231044270.22634-100000@melkor>; from vivienc@nerim.net on Thu, Jan 23, 2003 at 10:59:29AM +0100
On Thu, Jan 23, 2003 at 10:59:29AM +0100, Vivien Chappelier wrote:
> > Shouldn't those two long's be replaced with u64 and u32
> > respectively? Is the second struct really meant to be twice the
> > size the first?
>
> They should be the same size, otherwise sys32_rt_sigsuspend and
> sys32_rt_sigaction will return EINVAL. As the comment says:
> /* XXX: Don't preclude handling different sized sigset_t's. */
>
> I've posted a patch to fix that earlier this month (Monday 13 Jan
> 2003 "[2.5 PATCH] signal handling").
Most of what your patch does is undoing an accidental commit of a signal
rework that wasn't yet supposed to go out.
Ralf
next prev parent reply other threads:[~2003-01-24 1:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-23 7:17 sigset_t32 broken? Andrew Clausen
2003-01-23 9:59 ` Vivien Chappelier
2003-01-24 1:48 ` Ralf Baechle [this message]
2003-01-27 0:44 ` Vivien Chappelier
2003-01-27 9:19 ` Geert Uytterhoeven
2003-01-27 22:30 ` Juan Quintela
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=20030124024854.B9031@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=clausen@melbourne.sgi.com \
--cc=linux-mips@linux-mips.org \
--cc=vivienc@nerim.net \
/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.