From: Nicholas Piggin <npiggin@gmail.com>
To: Florian Weimer <fw@deneb.enyo.de>
Cc: Adhemerval Zanella <adhemerval.zanella@linaro.org>,
Rich Felker <dalias@libc.org>,
David Laight <David.Laight@ACULAB.COM>,
"libc-alpha@sourceware.org" <libc-alpha@sourceware.org>,
"libc-dev@lists.llvm.org" <libc-dev@lists.llvm.org>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
musl@lists.openwall.com,
Segher Boessenkool <segher@kernel.crashing.org>
Subject: Re: [musl] Re: Powerpc Linux 'scv' system call ABI proposal take 2
Date: Wed, 22 Apr 2020 17:31:07 +1000 [thread overview]
Message-ID: <1587540390.vde84z8edw.astroid@bobo.none> (raw)
In-Reply-To: <874ktcng8z.fsf@mid.deneb.enyo.de>
Excerpts from Florian Weimer's message of April 22, 2020 5:15 pm:
> * Nicholas Piggin:
>
>> Another option would be to use a different signal. I don't see that any
>> are more suitable.
>
> SIGSYS comes to my mind. But I don't know how exclusively it is
> associated with seccomp these days.
SIGSYS is entirely seccomp now. There looks like a single obscure MIPS
user of it in Linux that's not seccomp, but it would be entirely new for
powerpc (or any of the common platforms, arm, x86 etc).
So I would be disinclined to use SIGSYS unless there are no other better
signal types, and we don't want to use SIGILL for some good reason -- is
there a good reason to add complexity for userspace by differentiating
these two situations?
Thanks,
Nick
next prev parent reply other threads:[~2020-04-22 7:33 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-15 21:45 [musl] " Nicholas Piggin
2020-04-15 22:55 ` Rich Felker
2020-04-16 0:16 ` Nicholas Piggin
2020-04-16 0:48 ` Rich Felker
2020-04-16 2:24 ` Nicholas Piggin
2020-04-16 2:35 ` Rich Felker
2020-04-16 2:53 ` Nicholas Piggin
2020-04-16 3:03 ` Rich Felker
2020-04-16 3:41 ` Nicholas Piggin
2020-04-16 20:18 ` Florian Weimer
2020-04-16 9:58 ` Szabolcs Nagy
2020-04-20 0:27 ` Nicholas Piggin
2020-04-20 1:29 ` Rich Felker
2020-04-20 2:08 ` Nicholas Piggin
2020-04-20 21:17 ` Szabolcs Nagy
2020-04-21 9:57 ` Florian Weimer
2020-04-16 15:21 ` Jeffrey Walton
2020-04-16 15:40 ` Rich Felker
2020-04-16 4:48 ` Florian Weimer
2020-04-16 15:35 ` Rich Felker
2020-04-16 16:42 ` Florian Weimer
2020-04-16 16:52 ` Rich Felker
2020-04-16 18:12 ` Florian Weimer
2020-04-16 23:02 ` Segher Boessenkool
2020-04-17 0:34 ` Rich Felker
2020-04-17 1:48 ` Segher Boessenkool
2020-04-17 8:34 ` Florian Weimer
2020-04-16 14:16 ` Adhemerval Zanella
2020-04-16 15:37 ` Rich Felker
2020-04-16 17:50 ` Adhemerval Zanella
2020-04-16 17:59 ` Rich Felker
2020-04-16 18:18 ` Adhemerval Zanella
2020-04-16 18:31 ` Rich Felker
2020-04-16 18:44 ` Rich Felker
2020-04-16 18:52 ` Adhemerval Zanella
2020-04-20 0:46 ` Nicholas Piggin
2020-04-20 1:10 ` Nicholas Piggin
2020-04-20 1:34 ` Rich Felker
2020-04-20 2:32 ` Nicholas Piggin
2020-04-20 4:09 ` Rich Felker
2020-04-20 4:31 ` Nicholas Piggin
2020-04-20 17:27 ` Rich Felker
2020-04-22 6:18 ` Nicholas Piggin
2020-04-22 6:29 ` Nicholas Piggin
2020-04-23 2:36 ` Rich Felker
2020-04-23 12:13 ` Adhemerval Zanella
2020-04-23 16:18 ` Rich Felker
2020-04-23 16:35 ` Adhemerval Zanella
2020-04-23 16:43 ` Rich Felker
2020-04-23 17:15 ` Adhemerval Zanella
2020-04-23 17:42 ` Rich Felker
2020-04-25 3:40 ` Nicholas Piggin
2020-04-25 4:52 ` Rich Felker
2020-04-25 3:30 ` Nicholas Piggin
2020-04-21 12:28 ` David Laight
2020-04-21 14:39 ` Rich Felker
2020-04-21 15:00 ` Adhemerval Zanella
2020-04-21 15:31 ` David Laight
2020-04-22 6:54 ` [musl] " Nicholas Piggin
2020-04-22 7:15 ` Florian Weimer
2020-04-22 7:31 ` Nicholas Piggin [this message]
2020-04-22 8:11 ` Florian Weimer
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=1587540390.vde84z8edw.astroid@bobo.none \
--to=npiggin@gmail.com \
--cc=David.Laight@ACULAB.COM \
--cc=adhemerval.zanella@linaro.org \
--cc=dalias@libc.org \
--cc=fw@deneb.enyo.de \
--cc=libc-alpha@sourceware.org \
--cc=libc-dev@lists.llvm.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=musl@lists.openwall.com \
--cc=segher@kernel.crashing.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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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).