From: Greg KH <gregkh@linuxfoundation.org>
To: Frank van der Linden <fllinden@amazon.com>
Cc: stable@vger.kernel.org, Daniel Borkmann <daniel@iogearbox.net>,
Alexei Starovoitov <ast@kernel.org>
Subject: Re: [PATCH 4.9] bpf: Add kconfig knob for disabling unpriv bpf by default
Date: Sun, 13 Feb 2022 12:10:40 +0100 [thread overview]
Message-ID: <YgjnMEHWI0kffEg4@kroah.com> (raw)
In-Reply-To: <20220212212149.6421-1-fllinden@amazon.com>
On Sat, Feb 12, 2022 at 09:21:49PM +0000, Frank van der Linden wrote:
> From: Daniel Borkmann <daniel@iogearbox.net>
>
> commit 08389d888287c3823f80b0216766b71e17f0aba5 upstream.
>
> Add a kconfig knob which allows for unprivileged bpf to be disabled by default.
> If set, the knob sets /proc/sys/kernel/unprivileged_bpf_disabled to value of 2.
>
> This still allows a transition of 2 -> {0,1} through an admin. Similarly,
> this also still keeps 1 -> {1} behavior intact, so that once set to permanently
> disabled, it cannot be undone aside from a reboot.
>
> We've also added extra2 with max of 2 for the procfs handler, so that an admin
> still has a chance to toggle between 0 <-> 2.
>
> Either way, as an additional alternative, applications can make use of CAP_BPF
> that we added a while ago.
>
> Signed-off-by: Daniel Borkmann <daniel@iogearbox.net>
> Signed-off-by: Alexei Starovoitov <ast@kernel.org>
> Link: https://lore.kernel.org/bpf/74ec548079189e4e4dffaeb42b8987bb3c852eee.1620765074.git.daniel@iogearbox.net
> [fllinden@amazon.com: backported to 4.9]
> Signed-off-by: Frank van der Linden <fllinden@amazon.com>
> ---
> Documentation/sysctl/kernel.txt | 21 +++++++++++++++++++++
> init/Kconfig | 10 ++++++++++
> kernel/bpf/syscall.c | 3 ++-
> kernel/sysctl.c | 29 +++++++++++++++++++++++++----
> 4 files changed, 58 insertions(+), 5 deletions(-)
Now queued up, thanks.
greg k-h
prev parent reply other threads:[~2022-02-13 11:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-12 21:21 [PATCH 4.9] bpf: Add kconfig knob for disabling unpriv bpf by default Frank van der Linden
2022-02-13 11:10 ` Greg KH [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YgjnMEHWI0kffEg4@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=ast@kernel.org \
--cc=daniel@iogearbox.net \
--cc=fllinden@amazon.com \
--cc=stable@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.