Re: [PATCH bpf-next] bpf, capabilities: introduce CAP_BPF

From
Alexei Starovoitov <hidden>
Date
2019-08-28 04:47:38
Also in
bpf, linux-api, netdev
Reply to
Masami Hiramatsu, 2019-08-28
On Wed, Aug 28, 2019 at 12:30:41PM +0900, Masami Hiramatsu wrote:
quoted
kprobes can be created in the tracefs filesystem (which is separate from
debugfs, tracefs just gets automatically mounted
in /sys/kernel/debug/tracing when debugfs is mounted) from the
kprobe_events file. /sys/kernel/tracing is just the tracefs
directory without debugfs, and was created specifically to allow
tracing to be access without opening up the can of worms in debugfs.
I like the CAP_TRACING for tracefs. Can we make the tracefs itself
check the CAP_TRACING and call file_ops? or each tracefs file-ops
handlers must check it?
Thanks for the feedback.
I'll hack a prototype of CAP_TRACING for perf bits that I understand
and you folks will be able to use it in ftrace when initial support lands.
imo the question above is an implementation detail that you can resolve later.
I see it as a followup to initial CAP_TRACING drop.
Thread (44 messages) 44 messages, 8 authors, last reply 2019-10-04
Keyboard shortcuts
hback out one level
jnext message in thread / next series-diff position
kprevious message in thread / previous series-diff position
ldrill in
Escclose help / fold thread tree
?toggle this help