From: "Alejandro Colomar (man-pages)" <alx.manpages@gmail.com>
To: Florian Weimer <fweimer@redhat.com>
Cc: Ivan Zuboff <anotherdiskmag@gmail.com>, libc-alpha@sourceware.org
Subject: Re: [PATCH] manual: SA_ONSTACK is ignored without alternate stack
Date: Thu, 3 Feb 2022 12:31:26 +0100 [thread overview]
Message-ID: <49f3ad83-3092-3e62-faef-b960a48cf290@gmail.com> (raw)
In-Reply-To: <87fsp0wa9p.fsf@oldenburg.str.redhat.com>
Hi Florian,
On 2/3/22 10:48, Florian Weimer wrote:
> The current stack is used. No SIGILL is generated.
>
> ---
Thanks for the help!
Alex
> manual/signal.texi | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/manual/signal.texi b/manual/signal.texi
> index 8a12baf044..5c2ba7dae6 100644
> --- a/manual/signal.texi
> +++ b/manual/signal.texi
> @@ -1329,7 +1329,7 @@ Setting this flag for a signal other than @code{SIGCHLD} has no effect.
> If this flag is set for a particular signal number, the system uses the
> signal stack when delivering that kind of signal. @xref{Signal Stack}.
> If a signal with this flag arrives and you have not set a signal stack,
> -the system terminates the program with @code{SIGILL}.
> +the normal user stack is used instead, as if the flag had not been set.
> @end deftypevr
>
> @deftypevr Macro int SA_RESTART
>
--
Alejandro Colomar
Linux man-pages comaintainer; http://www.kernel.org/doc/man-pages/
http://www.alejandro-colomar.es/
prev parent reply other threads:[~2022-02-03 11:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-03 9:48 Florian Weimer
2022-02-03 11:31 ` Alejandro Colomar (man-pages) [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=49f3ad83-3092-3e62-faef-b960a48cf290@gmail.com \
--to=alx.manpages@gmail.com \
--cc=anotherdiskmag@gmail.com \
--cc=fweimer@redhat.com \
--cc=libc-alpha@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).