From: Richard Henderson <rth@twiddle.net>
To: roland@redhat.com, linux-arch@vger.kernel.org
Subject: waitid fallout
Date: Tue, 14 Sep 2004 20:39:03 -0700 [thread overview]
Message-ID: <20040915033903.GA904@twiddle.net> (raw)
Is an *entire* struct rusage required in siginfo_t for sigchld?
It's much bigger than the 24 (!) words of padding we had reserved
for expansion in siginfo_t.
Which means that the size of siginfo_t changed, which means that
any existing "sigwaitinfo ({ SIGCHLD }, &info)" will now corrupt
user memory. Perhaps we think no one does this, but we should
at least be aware of the ABI change.
Alpha is not yet using a VDSO for the signal frame unwind info, so
I noticed that all of my signal cancelation tests are now failing,
because the layout of the signal frame changed. Perhaps I'll take
this opportunity to update, but it does require a rather coordinated
kernel + libc upgrade in order to keep things working smoothly...
r~
next reply other threads:[~2004-09-15 3:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-15 3:39 Richard Henderson [this message]
2004-09-15 4:37 ` waitid fallout Stephen Rothwell
2004-09-15 5:34 ` Roland McGrath
2004-09-15 6:19 ` Richard Henderson
2004-09-18 13:03 ` Arnd Bergmann
2004-09-20 21:27 ` Roland McGrath
2004-09-15 4:49 ` Richard Henderson
2004-09-15 6:23 ` Andi Kleen
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=20040915033903.GA904@twiddle.net \
--to=rth@twiddle.net \
--cc=linux-arch@vger.kernel.org \
--cc=roland@redhat.com \
/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