From: Mike Frysinger <vapier@gentoo.org>
To: Helge Deller <deller@gmx.de>
Cc: John David Anglin <dave.anglin@bell.net>,
linux-parisc List <linux-parisc@vger.kernel.org>
Subject: Re: struct sigaction sa_restorer field
Date: Sun, 10 Aug 2014 09:49:52 -0400 [thread overview]
Message-ID: <108312262.dGJ5C12eXd@vapier> (raw)
In-Reply-To: <trinity-72a99ebc-405d-44c1-8c8b-0a04a9b401b3-1405931146850@3capp-gmx-bs43>
[-- Attachment #1: Type: text/plain, Size: 852 bytes --]
On Mon 21 Jul 2014 10:25:46 Helge Deller wrote:
> > The sa_restorer field is obsolete and not in the hppa struct
> > sigaction, but we still define SA_RESTORER. What should be done?
>
> Basically to not break userspace we can't (and shouldn't) add the
> sa_restorer struct member. So, the only option would be to drop the
> SA_RESTORER #define, right? But I have no idea how and if this will break
> some builds, since the major arches seem to define SA_RESTORER...
would be nice to drop. i had to update strace to undef it for hppa since the
field didn't actually exist -- it uses the define to see whether the field
should be decoded (which is why strace decoding of this syscall hasn't worked
in the past on parisc). not all arches define it, so i think there's already
cover for code needing to check for its existence.
-mike
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2014-08-10 13:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-20 23:32 struct sigaction sa_restorer field John David Anglin
2014-07-21 8:25 ` Helge Deller
2014-07-21 14:14 ` John David Anglin
2014-07-21 15:30 ` Aw: " Helge Deller
2014-08-10 13:49 ` Mike Frysinger [this message]
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=108312262.dGJ5C12eXd@vapier \
--to=vapier@gentoo.org \
--cc=dave.anglin@bell.net \
--cc=deller@gmx.de \
--cc=linux-parisc@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