[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200224205028.0f283991@heffalump.sk2.org>
Date: Mon, 24 Feb 2020 20:50:28 +0100
From: Stephen Kitt <steve@....org>
To: Alexei Starovoitov <alexei.starovoitov@...il.com>
Cc: Jonathan Corbet <corbet@....net>,
Alexei Starovoitov <ast@...nel.org>,
Daniel Borkmann <daniel@...earbox.net>,
Martin KaFai Lau <kafai@...com>,
Song Liu <songliubraving@...com>, Yonghong Song <yhs@...com>,
Andrii Nakryiko <andriin@...com>, bpf <bpf@...r.kernel.org>,
"open list:DOCUMENTATION" <linux-doc@...r.kernel.org>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] docs: sysctl/kernel: document BPF entries
On Sun, 23 Feb 2020 14:44:31 -0800, Alexei Starovoitov
<alexei.starovoitov@...il.com> wrote:
> On Fri, Feb 21, 2020 at 10:18 AM Stephen Kitt <steve@....org> wrote:
> > @@ -1152,6 +1166,16 @@ NMI switch that most IA32 servers have fires
> > unknown NMI up, for example. If a system hangs up, try pressing the NMI
> > switch.
> >
> >
> > +unprivileged_bpf_disabled
> > +=========================
> > +
> > +Writing 1 to this entry will disabled unprivileged calls to ``bpf()``;
>
> 'will disable' ?
Indeed, thanks.
> It doesn't apply to bpf-next with:
> error: sha1 information is lacking or useless
> (Documentation/admin-guide/sysctl/kernel.rst).
> error: could not build fake ancestor
> Patch failed at 0001 docs: sysctl/kernel: Document BPF entries
Sorry, I forgot to include the base commit information; this is against
8f21f54b8a95 in docs-next.
I’ll wait for that to make it to Linus’ tree and re-submit the patch (with
the fix above).
Regards,
Stephen
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists