linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alexei Starovoitov <ast@plumgrid.com>
To: "David S. Miller" <davem@davemloft.net>
Cc: Andy Lutomirski <luto@amacapital.net>,
	Ingo Molnar <mingo@kernel.org>,
	Hannes Frederic Sowa <hannes@stressinduktion.org>,
	Eric Dumazet <edumazet@google.com>,
	Daniel Borkmann <daniel@iogearbox.net>,
	Kees Cook <keescook@chromium.org>,
	linux-api@vger.kernel.org, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next 1/2] bpf: enable non-root eBPF programs
Date: Wed, 7 Oct 2015 19:29:16 -0700	[thread overview]
Message-ID: <5615D4FC.1010706@plumgrid.com> (raw)
In-Reply-To: <1444078101-29060-2-git-send-email-ast@plumgrid.com>

On 10/5/15 1:48 PM, Alexei Starovoitov wrote:
> Unprivileged socket filter bpf programs have access to the
> following helper functions:
> - map lookup/update/delete (but they cannot store kernel pointers into them)
> - get_random (it's already exposed to unprivileged user space)
> - get_smp_processor_id
> - tail_call into another socket filter program
> - ktime_get_ns
> - bpf_trace_printk (for debugging)

while reviewing everything for Nth time realized that
bpf_trace_printk is useless for unprivileged users, since
trace_pipe is root only.
So going to drop it in V2.


  parent reply	other threads:[~2015-10-08  2:29 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-05 20:48 [PATCH net-next 0/2] bpf: unprivileged Alexei Starovoitov
2015-10-05 20:48 ` [PATCH net-next 1/2] bpf: enable non-root eBPF programs Alexei Starovoitov
2015-10-05 21:00   ` Kees Cook
2015-10-05 21:12     ` Alexei Starovoitov
2015-10-05 21:16       ` Andy Lutomirski
2015-10-05 21:32         ` Alexei Starovoitov
2015-10-05 22:02       ` Kees Cook
2015-10-06  0:28         ` Alexei Starovoitov
2015-10-05 22:14   ` Daniel Borkmann
2015-10-06  0:51     ` Alexei Starovoitov
2015-10-06  7:13       ` Ingo Molnar
2015-10-06  8:05         ` Daniel Borkmann
2015-10-06  8:20           ` Ingo Molnar
2015-10-06  8:39             ` Daniel Borkmann
2015-10-06 17:50               ` Alexei Starovoitov
2015-10-06 17:56                 ` Eric Dumazet
2015-10-06 18:05                   ` Andy Lutomirski
2015-10-07  6:05                     ` Ingo Molnar
2015-10-06 19:26                   ` Alexei Starovoitov
2015-10-06 18:03                 ` Daniel Borkmann
2015-10-06 12:45       ` Daniel Borkmann
2015-10-07 21:20         ` Alexei Starovoitov
2015-10-07 22:07           ` Daniel Borkmann
2015-10-07 22:22             ` Kees Cook
2015-10-07 23:49               ` Alexei Starovoitov
2015-10-08  6:21                 ` Ingo Molnar
2015-10-08  6:30                   ` Alexei Starovoitov
2015-10-08 17:42                 ` Kees Cook
2015-10-08  2:29   ` Alexei Starovoitov [this message]
2015-10-05 20:48 ` [PATCH net-next 2/2] bpf: charge user for creation of BPF maps and programs Alexei Starovoitov

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=5615D4FC.1010706@plumgrid.com \
    --to=ast@plumgrid.com \
    --cc=daniel@iogearbox.net \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=hannes@stressinduktion.org \
    --cc=keescook@chromium.org \
    --cc=linux-api@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@amacapital.net \
    --cc=mingo@kernel.org \
    --cc=netdev@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 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).