From: Dev Jain <dev.jain@arm.com>
To: alx@kernel.org, linux-man@vger.kernel.org
Cc: mingo@kernel.org, tglx@linutronix.de, mark.rutland@arm.com,
ryan.roberts@arm.com, broonie@kernel.org, suzuki.poulose@arm.com,
Anshuman.Khandual@arm.com, DeepakKumar.Mishra@arm.com,
aneesh.kumar@kernel.org, linux-kernel@vger.kernel.org,
Dev Jain <dev.jain@arm.com>
Subject: [PATCH v2 1/2] signal.7: Clearly describe ucontext kernel dump to userspace
Date: Tue, 11 Jun 2024 14:38:22 +0530 [thread overview]
Message-ID: <20240611090823.820724-2-dev.jain@arm.com> (raw)
In-Reply-To: <20240611090823.820724-1-dev.jain@arm.com>
The set of blocked signals is updated from struct sigaction after the
kernel dumps ucontext. Mention this to avoid misunderstanding.
Signed-off-by: Dev Jain <dev.jain@arm.com>
---
man/man7/signal.7 | 8 +++++++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff --git a/man/man7/signal.7 b/man/man7/signal.7
index 4ba5306c8..7d22a7cfe 100644
--- a/man/man7/signal.7
+++ b/man/man7/signal.7
@@ -282,7 +282,13 @@ the thread's alternate signal stack settings.
.B SA_SIGINFO
flag, then the above information is accessible via the
.I ucontext_t
-object that is pointed to by the third argument of the signal handler.)
+object that is pointed to by the third argument of the signal handler.
+This object reflects the state at which the signal is delivered, rather
+than in the handler;
+for example, the mask of blocked signals stored in this object will not
+contain the mask of new signals blocked through
+.BR sigaction(2)).
+
.IP (1.4)
Any signals specified in
.I act\->sa_mask
--
2.34.1
next prev parent reply other threads:[~2024-06-11 9:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-11 9:08 [PATCH v2 0/2] signal(7) fixes Dev Jain
2024-06-11 9:08 ` Dev Jain [this message]
2024-06-17 10:54 ` [PATCH v2 1/2] signal.7: Clearly describe ucontext kernel dump to userspace Alejandro Colomar
2024-06-17 10:56 ` Alejandro Colomar
2024-06-11 9:08 ` [PATCH v2 2/2] signal.7: Fix wrong mention of sigprocmask Dev Jain
2024-06-11 13:06 ` Mark Brown
2024-06-17 10:59 ` Alejandro Colomar
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=20240611090823.820724-2-dev.jain@arm.com \
--to=dev.jain@arm.com \
--cc=Anshuman.Khandual@arm.com \
--cc=DeepakKumar.Mishra@arm.com \
--cc=alx@kernel.org \
--cc=aneesh.kumar@kernel.org \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@kernel.org \
--cc=ryan.roberts@arm.com \
--cc=suzuki.poulose@arm.com \
--cc=tglx@linutronix.de \
/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