From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mailbackend.panix.com (mailbackend.panix.com [166.84.1.89]) by sourceware.org (Postfix) with ESMTPS id 8BF253850402 for ; Sun, 25 Apr 2021 19:12:19 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 8BF253850402 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=panix.com Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=zackw@panix.com Received: from mail-yb1-f181.google.com (mail-yb1-f181.google.com [209.85.219.181]) by mailbackend.panix.com (Postfix) with ESMTPSA id 4FSyMQ6GMWzSBT for ; Sun, 25 Apr 2021 15:12:18 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=panix.com; s=panix; t=1619377938; bh=fc/8Z24Q3s7ry5U7i5eSbitrtiEv2nEp2QWukNso8Fk=; h=References:In-Reply-To:From:Date:Subject:To:Cc; b=S0FXHKAhUNVvtIs5fxf4gQ+WNFyJSmVvDDnV8vqkSw7apP7Lkxt+ctwtH6VO7ijID D5XiVh4U1npXIj3QZgIggNV3nX8z1bEQlw0X3nKmsAvJxCJoeSzxq1/mpJioaEDPF9 rM77NDYK1rChJlCtq5oSDCoTq6coC44op7TXIEtU= Received: by mail-yb1-f181.google.com with SMTP id s9so3746397ybe.5 for ; Sun, 25 Apr 2021 12:12:18 -0700 (PDT) X-Gm-Message-State: AOAM533yDCbXLAFnUlQyUaAxJv3yu2LrWLTcMEAS7Ep7sIGgDJdiFrgW UxMz5mBjujY6ao+n2V+ir637j4kATrJmvmPMJhs= X-Google-Smtp-Source: ABdhPJycnxXfPvnAKFw8qjAuPfEP8YLOtME9eW25HtgDz3bgNkXBYyEwiEg66nLD8lKmSL8IWhm9Tz9HXbpRgD+UJVk= X-Received: by 2002:a25:4943:: with SMTP id w64mr9475524yba.256.1619377938461; Sun, 25 Apr 2021 12:12:18 -0700 (PDT) MIME-Version: 1.0 References: <20210423230609.13519-1-alx.manpages@gmail.com> <56932c68-4992-c5e4-819f-a88f60b3f63a@gmail.com> In-Reply-To: From: Zack Weinberg Date: Sun, 25 Apr 2021 15:12:05 -0400 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [RFC] bpf.2: Use standard types and attributes To: Alexei Starovoitov Cc: "Alejandro Colomar (man-pages)" , linux-man , GNU C Library , LKML , gcc-patches@gcc.gnu.org, "Michael Kerrisk (man-pages)" , bpf Content-Type: text/plain; charset="UTF-8" X-Spam-Status: No, score=-1.7 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, JMQ_SPF_NEUTRAL, RCVD_IN_MSPIKE_H3, RCVD_IN_MSPIKE_WL, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=no autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org X-BeenThere: gcc-patches@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc-patches mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Apr 2021 19:12:20 -0000 On Sun, Apr 25, 2021 at 12:52 PM Alexei Starovoitov via Libc-alpha wrote: > On Sat, Apr 24, 2021 at 10:56 AM Alejandro Colomar (man-pages) > wrote: > > > > Hello Alexei, > > > > On 4/24/21 1:20 AM, Alexei Starovoitov wrote: > > > Nack. > > > The man page should describe the kernel api the way it is in .h file. > > > > Why? > > Because man page must describe the linux uapi headers the way they > are installed in the system and not invent alternative implementations. > The users will include those .h with __u32 and will see them in their code. > Man page saying something else is a dangerous lie. Why do you consider it _dangerous_ for the manpages to replace __u32 with uint32_t, when we know by construction that the two types will always be the same? Alejandro's preference for the types standardized by ISO C seems perfectly reasonable to me for documentation; people reading the documentation can be expected to already know what they mean, unlike the Linux-specifc __[iu]NN types. Also, all else being equal, documentation should avoid use of symbols in the ISO C reserved namespace. If anything I would argue that it is the uapi headers that should be changed, to use the types. zw