All of lore.kernel.org
 help / color / mirror / Atom feed
From: Florian Weimer <fweimer@redhat.com>
To: linux-man@vger.kernel.org
Subject: [PATCH] sigalstack.2: Mention the need for separate signal stacks for threads
Date: Tue, 18 May 2021 22:40:38 +0200	[thread overview]
Message-ID: <87h7iz4vy1.fsf@oldenburg.str.redhat.com> (raw)

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


             reply	other threads:[~2021-05-18 20:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-18 20:40 Florian Weimer [this message]
2021-05-21 11:11 ` [PATCH] sigalstack.2: Mention the need for separate signal stacks for threads Alejandro Colomar (man-pages)

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=87h7iz4vy1.fsf@oldenburg.str.redhat.com \
    --to=fweimer@redhat.com \
    --cc=linux-man@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 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.