Messages in this thread | | | Date | Mon, 02 Jun 2014 19:04:38 +0200 | From | Daniel Borkmann <> | Subject | Re: [PATCH v2 net-next 0/2] split BPF out of core networking |
| |
On 06/02/2014 05:41 PM, Alexei Starovoitov wrote: ... > Glad you brought up this point :) > 100% agree that current double verification done by seccomp is far from > being generic and quite hard to maintain, since any change done to > classic BPF verifier needs to be thought through from seccomp_check_filter() > perspective as well.
Glad we're on the same page.
> BPF's input context, set of allowed calls need to be expressed in a generic way. > Obviously this split by itself won't make classic BPF all of a sudden generic. > It rather defines a boundary of eBPF core.
Note, I'm not at all against using it in tracing, I think it's probably a good idea, but shouldn't we _first_ think about how to overcome such deficits as above by improving upon its in-kernel API design, thus to better prepare it to be generic? I feel this step is otherwise just skipped and quickly 'hacked' around ... ;)
| |