From: Quentin Monnet <quentin@isovalent.com>
To: Milan Landaverde <milan@mdaverde.com>
Cc: "Alexei Starovoitov" <ast@kernel.org>,
"Daniel Borkmann" <daniel@iogearbox.net>,
"Andrii Nakryiko" <andrii@kernel.org>,
"Martin KaFai Lau" <kafai@fb.com>,
"Song Liu" <songliubraving@fb.com>, "Yonghong Song" <yhs@fb.com>,
"John Fastabend" <john.fastabend@gmail.com>,
"KP Singh" <kpsingh@kernel.org>,
"Paul Chaignon" <paul@isovalent.com>,
"Niklas Söderlund" <niklas.soderlund@corigine.com>,
netdev@vger.kernel.org, bpf@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH bpf-next] bpf/bpftool: add unprivileged_bpf_disabled check against value of 2
Date: Tue, 22 Mar 2022 15:54:01 +0000 [thread overview]
Message-ID: <ca7b331c-bd35-7d51-3df4-723bc36676f8@isovalent.com> (raw)
In-Reply-To: <20220322145012.1315376-1-milan@mdaverde.com>
2022-03-22 10:49 UTC-0400 ~ Milan Landaverde <milan@mdaverde.com>
> In [1], we added a kconfig knob that can set
> /proc/sys/kernel/unprivileged_bpf_disabled to 2
>
> We now check against this value in bpftool feature probe
>
> [1] https://lore.kernel.org/bpf/74ec548079189e4e4dffaeb42b8987bb3c852eee.1620765074.git.daniel@iogearbox.net
>
> Signed-off-by: Milan Landaverde <milan@mdaverde.com>
Acked-by: Quentin Monnet <quentin@isovalent.com>
Thanks!
next prev parent reply other threads:[~2022-03-22 15:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-22 14:49 [PATCH bpf-next] bpf/bpftool: add unprivileged_bpf_disabled check against value of 2 Milan Landaverde
2022-03-22 15:54 ` Quentin Monnet [this message]
2022-03-22 17:39 ` KP Singh
2022-03-29 2:20 ` patchwork-bot+netdevbpf
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=ca7b331c-bd35-7d51-3df4-723bc36676f8@isovalent.com \
--to=quentin@isovalent.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=john.fastabend@gmail.com \
--cc=kafai@fb.com \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=milan@mdaverde.com \
--cc=netdev@vger.kernel.org \
--cc=niklas.soderlund@corigine.com \
--cc=paul@isovalent.com \
--cc=songliubraving@fb.com \
--cc=yhs@fb.com \
/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.