From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id E0624C4332F for ; Tue, 12 Apr 2022 13:55:58 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1356152AbiDLN6O (ORCPT ); Tue, 12 Apr 2022 09:58:14 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:60336 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1356488AbiDLN5w (ORCPT ); Tue, 12 Apr 2022 09:57:52 -0400 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id 2092B5F95 for ; Tue, 12 Apr 2022 06:55:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1649771733; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version: content-transfer-encoding:content-transfer-encoding; bh=DryO9o3h8DdJ7OKPTCk6vR2g7q8n5OI79qGZDX0ru7M=; b=D5El+Ao3RXb3JUMnQQe/dcbOVt9B7gMjNNAfvmD5k+SELCZIWacfvk/wiLEVp76Gzq4W4w Hzpn6dKgoWpp9hignwrDGjh5ok+wrgrKUIJNDNiKKRGHf95bEGzc6ABnsF9XDosKaxiuDk QPceTXsmSvjtvIcG+gwLcm4y/AwjiWI= Received: from mimecast-mx02.redhat.com (mimecast-mx02.redhat.com [66.187.233.88]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-486-uQKBqyvsOcOEufdJ_mMTiw-1; Tue, 12 Apr 2022 09:55:31 -0400 X-MC-Unique: uQKBqyvsOcOEufdJ_mMTiw-1 Received: from smtp.corp.redhat.com (int-mx10.intmail.prod.int.rdu2.redhat.com [10.11.54.10]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 71FD7101A52C; Tue, 12 Apr 2022 13:55:31 +0000 (UTC) Received: from x1carbon.redhat.com (unknown [10.40.192.176]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 79317416159; Tue, 12 Apr 2022 13:55:30 +0000 (UTC) From: Arjun Shankar To: linux-man@vger.kernel.org Cc: Alejandro Colomar , Michael Kerrisk Subject: [PATCH] pthread_atfork.3: Remove a confusing reference to the current thread Date: Tue, 12 Apr 2022 15:55:20 +0200 Message-Id: <20220412135520.2388424-1-arjun@redhat.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Scanned-By: MIMEDefang 2.85 on 10.11.54.10 Precedence: bulk List-ID: X-Mailing-List: linux-man@vger.kernel.org The reference to "this thread" in the DESCRIPTION of pthread_atfork(3) could be incorrectly interpreted to mean that only handlers registered by the thread calling fork(2) are executed. Therefore, remove the reference. Signed-off-by: Arjun Shankar --- man3/pthread_atfork.3 | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/man3/pthread_atfork.3 b/man3/pthread_atfork.3 index b727cb48e..db5e210d4 100644 --- a/man3/pthread_atfork.3 +++ b/man3/pthread_atfork.3 @@ -39,7 +39,7 @@ The .BR pthread_atfork () function registers fork handlers that are to be executed when .BR fork (2) -is called by this thread. +is called. The handlers are executed in the context of the thread that calls .BR fork (2). .PP -- 2.34.1