[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAADnVQ+bPMsfva8YyAfvmXATDcykSkznskEtQueu=GKhOnYeZQ@mail.gmail.com>
Date: Tue, 4 May 2021 14:23:36 -0700
From: Alexei Starovoitov <alexei.starovoitov@...il.com>
To: Zack Weinberg <zackw@...ix.com>
Cc: Daniel Borkmann <daniel@...earbox.net>,
"Alejandro Colomar (man-pages)" <alx.manpages@...il.com>,
Greg KH <gregkh@...uxfoundation.org>,
"Michael Kerrisk (man-pages)" <mtk.manpages@...il.com>,
linux-man <linux-man@...r.kernel.org>,
LKML <linux-kernel@...r.kernel.org>,
glibc <libc-alpha@...rceware.org>, GCC <gcc-patches@....gnu.org>,
bpf <bpf@...r.kernel.org>,
Joseph Myers <joseph@...esourcery.com>,
David Laight <David.Laight@...lab.com>,
David Miller <davem@...emloft.net>
Subject: Re: [RFC v2] bpf.2: Use standard types and attributes
On Tue, May 4, 2021 at 1:33 PM Zack Weinberg <zackw@...ix.com> wrote:
> the information that should
> appear in the manpages is the information that is most relevant to
> user space programmers.
The bpf programs are compiled for the kernel and run in the kernel.
Hence bpf man pages must reflect the kernel.
Also there is BTF where type names are part of the verification process.
if a user decides to rename a type it will be rejected by the kernel verifier.
Powered by blists - more mailing lists