All of lore.kernel.org
 help / color / mirror / Atom feed
* [PATCH] sigalstack.2: Mention the need for separate signal stacks for threads
@ 2021-05-18 20:40 Florian Weimer
  2021-05-21 11:11 ` Alejandro Colomar (man-pages)
  0 siblings, 1 reply; 2+ messages in thread
From: Florian Weimer @ 2021-05-18 20:40 UTC (permalink / raw)
  To: linux-man

Signed-off-by: Florian Weimer <fweimer@redhat.com>

---
 man2/sigaltstack.2 | 7 +++++--
 1 file changed, 5 insertions(+), 2 deletions(-)

diff --git a/man2/sigaltstack.2 b/man2/sigaltstack.2
index 53268ccbe..1510a98ab 100644
--- a/man2/sigaltstack.2
+++ b/man2/sigaltstack.2
@@ -54,7 +54,10 @@ alternate signal stack.
 An alternate signal stack is used during the
 execution of a signal handler if the establishment of that handler (see
 .BR sigaction (2))
-requested it.
+requested it using the
+.B SA_ONSTACK
+flag.  Each thread that can execute such signal handlers needs its own
+separate alternate signal stack.
 .PP
 The normal sequence of events for using an alternate signal stack
 is the following:
@@ -67,7 +70,7 @@ signal stack.
 Use
 .BR sigaltstack ()
 to inform the system of the existence and
-location of the alternate signal stack.
+location of the alternate signal stack for the current thread.
 .TP
 3.
 When establishing a signal handler using


^ permalink raw reply related	[flat|nested] 2+ messages in thread

* Re: [PATCH] sigalstack.2: Mention the need for separate signal stacks for threads
  2021-05-18 20:40 [PATCH] sigalstack.2: Mention the need for separate signal stacks for threads Florian Weimer
@ 2021-05-21 11:11 ` Alejandro Colomar (man-pages)
  0 siblings, 0 replies; 2+ messages in thread
From: Alejandro Colomar (man-pages) @ 2021-05-21 11:11 UTC (permalink / raw)
  To: Florian Weimer; +Cc: linux-man, Michael Kerrisk (man-pages)

[CC += mtk]

Hi Florian,

On 5/18/21 10:40 PM, Florian Weimer wrote:
> Signed-off-by: Florian Weimer <fweimer@redhat.com>
> 

I don't understand how this works, so I'll CC Michael so that he merges it.

Thanks,

Alex

> ---
>   man2/sigaltstack.2 | 7 +++++--
>   1 file changed, 5 insertions(+), 2 deletions(-)
> 
> diff --git a/man2/sigaltstack.2 b/man2/sigaltstack.2
> index 53268ccbe..1510a98ab 100644
> --- a/man2/sigaltstack.2
> +++ b/man2/sigaltstack.2
> @@ -54,7 +54,10 @@ alternate signal stack.
>   An alternate signal stack is used during the
>   execution of a signal handler if the establishment of that handler (see
>   .BR sigaction (2))
> -requested it.
> +requested it using the
> +.B SA_ONSTACK
> +flag.  Each thread that can execute such signal handlers needs its own
> +separate alternate signal stack.
>   .PP
>   The normal sequence of events for using an alternate signal stack
>   is the following:
> @@ -67,7 +70,7 @@ signal stack.
>   Use
>   .BR sigaltstack ()
>   to inform the system of the existence and
> -location of the alternate signal stack.
> +location of the alternate signal stack for the current thread.
>   .TP
>   3.
>   When establishing a signal handler using
> 


-- 
Alejandro Colomar
Linux man-pages comaintainer; https://www.kernel.org/doc/man-pages/
Senior SW Engineer; http://www.alejandro-colomar.es/

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2021-05-21 11:11 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-05-18 20:40 [PATCH] sigalstack.2: Mention the need for separate signal stacks for threads Florian Weimer
2021-05-21 11:11 ` Alejandro Colomar (man-pages)

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.