From: Richard Palethorpe <rpalethorpe@suse.de>
To: "Michael Kerrisk \(man-pages\)" <mtk.manpages@gmail.com>
Cc: Richard Palethorpe <rpalethorpe@suse.com>,
linux-man@vger.kernel.org, ast@plumgrid.com, davem@davemloft.net,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>
Subject: Re: [PATCH] bpf.2: Change note on unprivileged access
Date: Fri, 17 Apr 2020 15:28:00 +0200 [thread overview]
Message-ID: <87h7xii6n3.fsf@our.domain.is.not.set> (raw)
In-Reply-To: <7f9476e0-a05a-c9ec-1135-87c641b93e32@gmail.com>
Hello Michael,
Michael Kerrisk (man-pages) <mtk.manpages@gmail.com> writes:
> Hello Richard,
>
> On 7/29/19 2:58 PM, Richard Palethorpe wrote:
>> This notes that the kernel now allows calls to bpf() without CAP_SYS_ADMIN
>> under some circumstances.
>
> Thanks. I have (at last) applied this patch.
:-)
>
> In Linux 4.4, the allowed BPF helper functions that could
> be called was, I think, governed by a check in sk_filter_func_proto().
> Nowadays (Linux 5.6), it is, I think, governed by the check in
> sk_filter_func_proto(). If that is the case, then probably there
It looks like bpf_base_func_proto() and sk_filter_func_proto(). Possibly
also cg_skb_func_proto() because it seems normal users can also attach a
cgroup skb filter program type (looking at bpf_prog_load() in syscall.c
for 5.7).
> are one or two more helper functions to be added to the list
> (e.g., get_numa_node_id, map_push_elem, map_pop_elem).
> Do you agree with my analysis?
Yes, at least those. IMO this is such a fast moving target it might be
best to direct users towards <linux/bpf.h>.
>
> Thanks,
>
> Michael
>
>> Signed-off-by: Richard Palethorpe <rpalethorpe@suse.com>
>> ---
>> man2/bpf.2 | 22 ++++++++++++++++++++--
>> 1 file changed, 20 insertions(+), 2 deletions(-)
>>
>> diff --git a/man2/bpf.2 b/man2/bpf.2
>> index b5c0869ae..a57ed9086 100644
>> --- a/man2/bpf.2
>> +++ b/man2/bpf.2
>> @@ -1120,11 +1120,29 @@ The
>> .BR bpf ()
>> system call is Linux-specific.
>> .SH NOTES
>> -In the current implementation, all
>> +Prior to Linux 4.4, all
>> .BR bpf ()
>> commands require the caller to have the
>> .B CAP_SYS_ADMIN
>> -capability.
>> +capability. From 4.4 onwards an unprivileged user may create limited
>> +programs of type
>> +.BR BPF_PROG_TYPE_SOCKET_FILTER
>> +and associated maps. However they may not store kernel pointers within
>> +the maps and are presently limited to the following helper functions:
>> +.IP * 3
>> +get_random
>> +.PD 0
>> +.IP *
>> +get_smp_processor_id
>> +.IP *
>> +tail_call
>> +.IP *
>> +ktime_get_ns
>> +.PD 1
>> +.PP
>> +Unprivileged access may be blocked by setting the sysctl
>> +.IR /proc/sys/kernel/unprivileged_bpf_disabled .
>> +.\" commit 1be7f75d1668d6296b80bf35dcf6762393530afc
>> .PP
>> eBPF objects (maps and programs) can be shared between processes.
>> For example, after
>>
--
Thank you,
Richard.
next prev parent reply other threads:[~2020-04-17 13:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190729125843.6319-1-rpalethorpe@suse.com>
2020-04-17 10:01 ` [PATCH] bpf.2: Change note on unprivileged access Michael Kerrisk (man-pages)
2020-04-17 13:28 ` Richard Palethorpe [this message]
2020-04-18 7:34 ` Michael Kerrisk (man-pages)
2020-04-18 7:36 ` Michael Kerrisk (man-pages)
2020-04-20 9:08 ` Quentin Monnet
2020-04-22 12:26 ` Michael Kerrisk (man-pages)
2020-04-23 9:56 ` Quentin Monnet
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=87h7xii6n3.fsf@our.domain.is.not.set \
--to=rpalethorpe@suse.de \
--cc=ast@kernel.org \
--cc=ast@plumgrid.com \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
--cc=rpalethorpe@suse.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).