From 934a35ac2bbbcf8cd65d8824fa824eb5c6170c88 Mon Sep 17 00:00:00 2001
From: Konstantin Belousov <kib@FreeBSD.org>
Date: Tue, 14 Apr 2026 02:42:51 +0300
Subject: [PATCH] libthr.3: describe SIGTHR

Explain how SIGTHR is used and that it should be not touched by user
code.  Note about SIGLIBRT.

Reviewed by:	emaste
Sponsored by:	The FreeBSD Foundation
MFC after:	3 days
Differential revision:	https://reviews.freebsd.org/D56384
---
 lib/libthr/libthr.3 | 19 +++++++++++++++++++
 1 file changed, 19 insertions(+)

diff --git a/lib/libthr/libthr.3 b/lib/libthr/libthr.3
index 8c7b8449054..5d9c5ec6706 100644
--- a/lib/libthr/libthr.3
+++ b/lib/libthr/libthr.3
@@ -269,6 +269,25 @@ the critical section.
 This should be taken into account when interpreting
 .Xr ktrace 1
 logs.
+.Pp
+The
+.Nm
+library uses the
+.Va SIGTHR
+signal for internal operations, in particular,
+for cancellation requests.
+This signal's masking and disposition is controlled by the library,
+and user programs should not try to modify them.
+The library interposes functions controlling signals to prevent
+inadvertent modifications and to guard portable code against
+exposure to
+.Va SIGTHR .
+.Pp
+Note: similarly, the
+.Va SIGLIBRT
+signal is reserved for use by
+.Lb librt ,
+and should be not modified by users.
 .Sh PROCESS-SHARED SYNCHRONIZATION OBJECTS
 In the
 .Li libthr