发自我的 iPhone
> 在 2015年10月21日，下午10:09，Peter Zijlstra <pet...@infradead.org> 写道： > > On Wed, Oct 21, 2015 at 10:01:46PM +0800, pi3orama wrote: >>> 在 2015年10月21日，下午9:49，Peter Zijlstra <pet...@infradead.org> 写道： >>> >>>> On Wed, Oct 21, 2015 at 09:42:12PM +0800, Wangnan (F) wrote: >>>> How can an eBPF program access a !local event: >>>> >>>> when creating perf event array we don't care which perf event >>>> is for which CPU, so perf program can access any perf event in >>>> that array. >>> >>> So what is stopping the eBPF thing from calling perf_event_read_local() >>> on a !local event and triggering a kernel splat? >> >> I can understand the perf_event_read_local() case, but I really can't >> understand >> what is stopping us to write to an atomic field belong to a !local perf >> event. >> Could you please give a further explanation? > > I simply do not get how this eBPF stuff works. > > Either I have access to !local events and I can hand one to > perf_event_read_local() and cause badness, or I do not have access to > !local events and the whole 'soft enable/disable' thing is simple. > > They cannot be both true. > > So explain; how does this eBPF stuff work. I think I get your point this time, and let me explain the eBPF stuff to you. You are aware that BPF programmer can break the system in this way: A=get_non_local_perf_event() perf_event_read_local(A) BOOM! However the above logic is impossible because BPF program can't work this way. First of all, it is impossible for a BPF program directly invoke a kernel function. Doesn't like kernel module, BPF program can only invoke functions designed for them, like what this patch does. So the ability of BPF programs is strictly restricted by kernel. If we don't allow BPF program call perf_event_read_local() across core, we can check this and return error in function we provide for them. Second: there's no way for a BPF program directly access a perf event. All perf events have to be wrapped by a map and be accessed by BPF functions described above. We don't allow BPF program fetch array element from that map. So pointers of perf event is safely protected from BPF program. In summary, your either-or logic doesn't hold in BPF world. A BPF program can only access perf event in a highly restricted way. We don't allow it calling perf_event_read_local() across core, so it can't. Thank you. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
