[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87ef14iffx.fsf@toke.dk>
Date: Thu, 29 Aug 2019 09:44:18 +0200
From: Toke Høiland-Jørgensen <toke@...hat.com>
To: Alexei Starovoitov <ast@...nel.org>, luto@...capital.net
Cc: davem@...emloft.net, peterz@...radead.org, rostedt@...dmis.org,
netdev@...r.kernel.org, bpf@...r.kernel.org, kernel-team@...com,
linux-api@...r.kernel.org
Subject: Re: [PATCH v2 bpf-next 1/3] capability: introduce CAP_BPF and CAP_TRACING
Alexei Starovoitov <ast@...nel.org> writes:
> CAP_BPF allows the following BPF operations:
> - Loading all types of BPF programs
> - Creating all types of BPF maps except:
> - stackmap that needs CAP_TRACING
> - devmap that needs CAP_NET_ADMIN
> - cpumap that needs CAP_SYS_ADMIN
Why CAP_SYS_ADMIN instead of CAP_NET_ADMIN for cpumap?
-Toke
Powered by blists - more mailing lists