From: "Joseph S. Myers" <joseph-qD8j1LwMmJjtCj0u4l0SBw@public.gmane.org>
To: linux-mips-6z/3iImG2C8G8FEW9MqTrA@public.gmane.org,
libc-alpha-9JcytcrH/bA+uJoB2kUjGw@public.gmane.org,
linux-api-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: MIPS MSA sigcontext changes in 3.15
Date: Tue, 17 Jun 2014 15:44:36 +0000 [thread overview]
Message-ID: <Pine.LNX.4.64.1406171539240.23412@digraph.polyomino.org.uk> (raw)
In-Reply-To: <Pine.LNX.4.64.1406171447030.23412-9YEB1lltEqivcGRMvF24k2I39yigxGEX@public.gmane.org>
On Tue, 17 Jun 2014, Joseph S. Myers wrote:
> signal mask at a particular offset in the ucontext. As far as I can see,
> extending sigcontext requires a new sigaction flag that could be used to
> opt in, for a particular signal handler, to receiving the new-layout
> ucontext (so new symbol versions of sigaction in glibc could then pass
> that flag to the kernel, but existing binaries would continue to get
> old-layout ucontext from the kernel), or else putting the new data at the
And a new flag would itself be problematic - signal handlers would need
wrapping with userspace code to convert structure layout when new-version
sigaction is used on an older kernel. That suggests putting the new data
at the end of ucontext is to be preferred (but in any case it would be
best to revert the incompatible changes until something compatible with
existing userspace can be produced).
--
Joseph S. Myers
joseph-qD8j1LwMmJjtCj0u4l0SBw@public.gmane.org
next prev parent reply other threads:[~2014-06-17 15:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-17 15:03 MIPS MSA sigcontext changes in 3.15 Joseph S. Myers
[not found] ` <Pine.LNX.4.64.1406171447030.23412-9YEB1lltEqivcGRMvF24k2I39yigxGEX@public.gmane.org>
2014-06-17 15:44 ` Joseph S. Myers [this message]
2014-06-17 16:25 ` Paul Burton
[not found] ` <Pine.LNX.4.64.1406171539240.23412-9YEB1lltEqivcGRMvF24k2I39yigxGEX@public.gmane.org>
2014-06-17 16:32 ` Matthew Fortune
2014-06-17 18:14 ` Paul Burton
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=Pine.LNX.4.64.1406171539240.23412@digraph.polyomino.org.uk \
--to=joseph-qd8j1lwmmjjtcj0u4l0sbw@public.gmane.org \
--cc=libc-alpha-9JcytcrH/bA+uJoB2kUjGw@public.gmane.org \
--cc=linux-api-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-mips-6z/3iImG2C8G8FEW9MqTrA@public.gmane.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).