From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dave Martin Subject: [PATCH 08/14] prctl.2: Work around bogus constant "maxsig" in PR_SET_PDEATHSIG Date: Tue, 12 May 2020 17:36:53 +0100 Message-ID: <1589301419-24459-9-git-send-email-Dave.Martin@arm.com> References: <1589301419-24459-1-git-send-email-Dave.Martin@arm.com> Return-path: Received: from foss.arm.com ([217.140.110.172]:58198 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727999AbgELQhx (ORCPT ); Tue, 12 May 2020 12:37:53 -0400 In-Reply-To: <1589301419-24459-1-git-send-email-Dave.Martin@arm.com> Sender: linux-arch-owner@vger.kernel.org List-ID: To: mtk.manpages@gmail.com Cc: linux-man@vger.kernel.org, linux-arch@vger.kernel.org, linux-arm-kernel@lists.infradead.org The description of PR_SET_PDEATHSIG refers to "maxsig", which is apparently intended to stand for the maximum defined signal number. maxsig seems not to be a thing, even in the kernel. Reword to use the standard constant NSIG. (Discussion of SIGRTMIN and SIGRTMAX seems out of scope here, and anyway is not relevant to the kernel.) Signed-off-by: Dave Martin --- man2/prctl.2 | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/man2/prctl.2 b/man2/prctl.2 index a84fb1d..1e04859 100644 --- a/man2/prctl.2 +++ b/man2/prctl.2 @@ -955,7 +955,9 @@ will operate in the privilege-restricting mode described above. .BR PR_SET_PDEATHSIG " (since Linux 2.1.57)" Set the parent-death signal of the calling process to \fIarg2\fP (either a signal value -in the range 1..maxsig, or 0 to clear). +in the range 1 .. +.BR NSIG " \-" +1, or 0 to clear). This is the signal that the calling process will get when its parent dies. .IP -- 2.1.4