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 X-Spam-Level: X-Spam-Status: No, score=-14.4 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,INCLUDES_CR_TRAILER,INCLUDES_PATCH, MAILING_LIST_MULTI,NICE_REPLY_A,SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED, USER_AGENT_SANE_1,WEIRD_QUOTING autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id C847AC4338F for ; Thu, 29 Jul 2021 10:24:14 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 9A32C604DC for ; Thu, 29 Jul 2021 10:24:14 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S235695AbhG2KYQ (ORCPT ); Thu, 29 Jul 2021 06:24:16 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:58172 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S235686AbhG2KYQ (ORCPT ); Thu, 29 Jul 2021 06:24:16 -0400 Received: from mail-wm1-x32c.google.com (mail-wm1-x32c.google.com [IPv6:2a00:1450:4864:20::32c]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 08F36C061757 for ; Thu, 29 Jul 2021 03:24:13 -0700 (PDT) Received: by mail-wm1-x32c.google.com with SMTP id n21so3366423wmq.5 for ; Thu, 29 Jul 2021 03:24:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=pLJd/P1l6EwU5fz/Bw3NOmQiHJV3obAaK4EKIcp7Z2U=; b=DWb5a4uQ9nSuKXzQVfrAqVYixEfSUPyGHX2cPMYEOl0ZawKgTfMKWRJd1Ev6gm2wcJ r5cYD/hjfwlFf248L8r/M1Q4uAZ2tzVaAtzCw8k1+v69LK37eX7qtAdQIkB9UyoQAasA gerykQ47KE/F8QUw77BhIoda52npwGlIgR8x+NBgClqUXl+KgG1Wibizr0Mce3xCRx+S v/7PFuzfj24rlVAiBqgOmInkzFV2hLINzWWSRBe/8eFV7TJRcQSG9XmTR3H1wmNc9602 rU6akCNuZylNgZn1kZvjRemgd/nyu1dicYaSif7Zh8Mq5V/CCpuBVf+N9IU2zk38Mxlp 1IQw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=pLJd/P1l6EwU5fz/Bw3NOmQiHJV3obAaK4EKIcp7Z2U=; b=Ir64CzazALazZBVsaupIUY+Fn5KJxzurkq8vgIUBWkrbFJXR7lbf+737/nHsbioLV0 /0t3XioxFQJkaJSZoepCDN03MDO7RHKD4nHGRrAWBDrlqNYt3BohrLr+AGg+vmCHQc0Y BZIEOIXHxUaHvjOpkOvFR6a8wtEPnPsrYIIjAeMaAnqTlG8xPOBpB5zi6QouZgJUCYDY Vkv03rBNdCWTb/CgLsiLHhNMmg048MQjI+qkipL5YDbm5vwFElYb78ib2/JyjtdCIrDs pIQ+m3/uBYVkW/a5NPGd4sbvweNK2GUApRJyw4v007TcVIIw+Pj5z8uCDQgaQLn4JsFJ ipLA== X-Gm-Message-State: AOAM531v25tmpGpClJz6VRV59FWJnxKSGRgvRWgProuXZFyUDHewvuxc wC+RnDRDYtcrRomsNYH039gzom+v3ZU= X-Google-Smtp-Source: ABdhPJzSpvbp0UK3CjytFo1a8unc568vK3xpGK5NE23XhcgJiZ+nEADb6CAD4H45jD2wYVVzv5kMKQ== X-Received: by 2002:a1c:f203:: with SMTP id s3mr13207085wmc.138.1627554251508; Thu, 29 Jul 2021 03:24:11 -0700 (PDT) Received: from [10.8.0.150] ([195.53.121.100]) by smtp.gmail.com with ESMTPSA id l3sm6684284wmq.2.2021.07.29.03.24.10 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 29 Jul 2021 03:24:11 -0700 (PDT) Subject: Re: [PATCH 11/32] futex.2: Minor tweaks to Kurt's patch To: mtk.manpages@gmail.com Cc: linux-man@vger.kernel.org References: <20210728202008.3158-1-alx.manpages@gmail.com> <20210728202008.3158-12-alx.manpages@gmail.com> From: "Alejandro Colomar (man-pages)" Message-ID: Date: Thu, 29 Jul 2021 12:24:10 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.11.0 MIME-Version: 1.0 In-Reply-To: <20210728202008.3158-12-alx.manpages@gmail.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-man@vger.kernel.org On 7/28/21 10:19 PM, Alejandro Colomar wrote: > Signed-off-by: Alejandro Colomar Drop this one too. > --- > man2/futex.2 | 69 ++++++++++++++++++++++++++-------------------------- > 1 file changed, 34 insertions(+), 35 deletions(-) > > diff --git a/man2/futex.2 b/man2/futex.2 > index 2f340e0e0..217b76734 100644 > --- a/man2/futex.2 > +++ b/man2/futex.2 > @@ -222,9 +222,9 @@ This allows the kernel to make some additional performance optimizations. > .\" taking reference counts on file backing store, and so on. > .IP > As a convenience, > -.IR > +.I > defines a set of constants with the suffix > -.BR _PRIVATE > +.B _PRIVATE > that are equivalents of all of the operations listed below, > .\" except the obsolete FUTEX_FD, for which the "private" flag was > .\" meaningless > @@ -247,19 +247,19 @@ This option bit can be employed only with the > and > (since Linux v5.14.0) > .\" commit bf22a6976897977b0a3f1aeba6823c959fc4fdae > -.BR FUTEX_LOCK_PI2 > +.B FUTEX_LOCK_PI2 > operations. > .IP > If this option is set, the kernel measures the > .I timeout > against the > -.BR CLOCK_REALTIME > +.B CLOCK_REALTIME > clock. > .IP > If this option is not set, the kernel measures the > .I timeout > against the > -.BR CLOCK_MONOTONIC > +.B CLOCK_MONOTONIC > clock. > .PP > The operation specified in > @@ -968,9 +968,8 @@ PI futexes are operated on by specifying one of the values listed below in > Note that the PI futex operations must be used as paired operations > and are subject to some additional requirements: > .IP * 3 > -.B FUTEX_LOCK_PI > -, > -.B FUTEX_LOCK_PI2 > +.BR FUTEX_LOCK_PI , > +.BR FUTEX_LOCK_PI2 , > and > .B FUTEX_TRYLOCK_PI > pair with > @@ -1123,7 +1122,7 @@ The > .IR uaddr2 , > .IR val , > and > -.IR val3 > +.I val3 > arguments are ignored. > .\" > .\"""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""" > @@ -1135,7 +1134,7 @@ This operation works similar like > .BR FUTEX_LOCK_PI . > The only difference is the > timeout argument. > -.BR FUTEX_LOCK_PI2 > +.B FUTEX_LOCK_PI2 > has support for selectable clocks. > .IP > If > @@ -1466,7 +1465,7 @@ The value pointed to by > is not equal to the expected value > .IR val3 . > .TP > -.BR EAGAIN > +.B EAGAIN > .RB ( FUTEX_LOCK_PI , > .BR FUTEX_LOCK_PI2 , > .BR FUTEX_TRYLOCK_PI , > @@ -1480,7 +1479,7 @@ is about to exit, > but has not yet handled the internal state cleanup. > Try again. > .TP > -.BR EDEADLK > +.B EDEADLK > .RB ( FUTEX_LOCK_PI , > .BR FUTEX_LOCK_PI2 , > .BR FUTEX_TRYLOCK_PI , > @@ -1522,18 +1521,18 @@ a spurious wakeup; since Linux 2.6.22, this no longer happens. > .TP > .B EINVAL > The operation in > -.IR futex_op > +.I futex_op > is one of those that employs a timeout, but the supplied > .I timeout > argument was invalid > .RI ( tv_sec > was less than zero, or > -.IR tv_nsec > +.I tv_nsec > was not less than 1,000,000,000). > .TP > .B EINVAL > The operation specified in > -.IR futex_op > +.I futex_op > employs one or both of the pointers > .I uaddr > and > @@ -1545,17 +1544,17 @@ the address is not four-byte-aligned. > .RB ( FUTEX_WAIT_BITSET , > .BR FUTEX_WAKE_BITSET ) > The bit mask supplied in > -.IR val3 > +.I val3 > is zero. > .TP > .B EINVAL > .RB ( FUTEX_CMP_REQUEUE_PI ) > .I uaddr > equals > -.IR uaddr2 > +.I uaddr2 > (i.e., an attempt was made to requeue to the same futex). > .TP > -.BR EINVAL > +.B EINVAL > .RB ( FUTEX_FD ) > The signal number supplied in > .I val > @@ -1570,9 +1569,9 @@ is invalid. > The kernel detected an inconsistency between the user-space state at > .I uaddr > and the kernel state\(emthat is, it detected a waiter which waits in > -.BR FUTEX_LOCK_PI > +.B FUTEX_LOCK_PI > or > -.BR FUTEX_LOCK_PI2 > +.B FUTEX_LOCK_PI2 > on > .IR uaddr . > .TP > @@ -1588,7 +1587,7 @@ This indicates either state corruption > or that the kernel found a waiter on > .I uaddr > which is waiting via > -.BR FUTEX_WAIT > +.B FUTEX_WAIT > or > .BR FUTEX_WAIT_BITSET . > .TP > @@ -1601,9 +1600,9 @@ and the kernel state; > .\" The kernel sees: I have non PI state for a futex you tried to > .\" tell me was PI > that is, the kernel detected a waiter which waits via > -.BR FUTEX_WAIT > +.B FUTEX_WAIT > or > -.BR FUTEX_WAIT_BITSET > +.B FUTEX_WAIT_BITSET > on > .IR uaddr2 . > .TP > @@ -1613,9 +1612,9 @@ The kernel detected an inconsistency between the user-space state at > .I uaddr > and the kernel state; > that is, the kernel detected a waiter which waits via > -.BR FUTEX_WAIT > +.B FUTEX_WAIT > or > -.BR FUTEX_WAIT_BITSET > +.B FUTEX_WAIT_BITSET > on > .IR uaddr . > .TP > @@ -1627,9 +1626,9 @@ and the kernel state; > that is, the kernel detected a waiter which waits on > .I uaddr > via > -.BR FUTEX_LOCK_PI > +.B FUTEX_LOCK_PI > or > -.BR FUTEX_LOCK_PI2 > +.B FUTEX_LOCK_PI2 > (instead of > .BR FUTEX_WAIT_REQUEUE_PI ). > .TP > @@ -1656,7 +1655,7 @@ Invalid argument. > .RB ( FUTEX_FD ) > The system-wide limit on the total number of open files has been reached. > .TP > -.BR ENOMEM > +.B ENOMEM > .RB ( FUTEX_LOCK_PI , > .BR FUTEX_LOCK_PI2 , > .BR FUTEX_TRYLOCK_PI , > @@ -1669,7 +1668,7 @@ Invalid operation specified in > .TP > .B ENOSYS > The > -.BR FUTEX_CLOCK_REALTIME > +.B FUTEX_CLOCK_REALTIME > option was specified in > .IR futex_op , > but the accompanying operation was neither > @@ -1679,7 +1678,7 @@ but the accompanying operation was neither > nor > .BR FUTEX_LOCK_PI2 . > .TP > -.BR ENOSYS > +.B ENOSYS > .RB ( FUTEX_LOCK_PI , > .BR FUTEX_LOCK_PI2 , > .BR FUTEX_TRYLOCK_PI , > @@ -1690,7 +1689,7 @@ A run-time check determined that the operation is not available. > The PI-futex operations are not implemented on all architectures and > are not supported on some CPU variants. > .TP > -.BR EPERM > +.B EPERM > .RB ( FUTEX_LOCK_PI , > .BR FUTEX_LOCK_PI2 , > .BR FUTEX_TRYLOCK_PI , > @@ -1703,11 +1702,11 @@ the futex at > .IR uaddr2 ). > (This may be caused by a state corruption in user space.) > .TP > -.BR EPERM > +.B EPERM > .RB ( FUTEX_UNLOCK_PI ) > The caller does not own the lock represented by the futex word. > .TP > -.BR ESRCH > +.B ESRCH > .RB ( FUTEX_LOCK_PI , > .BR FUTEX_LOCK_PI2 , > .BR FUTEX_TRYLOCK_PI , > @@ -1716,7 +1715,7 @@ The thread ID in the futex word at > .I uaddr > does not exist. > .TP > -.BR ESRCH > +.B ESRCH > .RB ( FUTEX_CMP_REQUEUE_PI ) > The thread ID in the futex word at > .I uaddr2 > @@ -1724,7 +1723,7 @@ does not exist. > .TP > .B ETIMEDOUT > The operation in > -.IR futex_op > +.I futex_op > employed the timeout specified in > .IR timeout , > and the timeout expired before the operation completed. > -- Alejandro Colomar Linux man-pages comaintainer; https://www.kernel.org/doc/man-pages/ http://www.alejandro-colomar.es/