Extending extended BPF

Posted Jul 10, 2014 6:03 UTC (Thu) by elanthis (guest, #6227)
Parent article: Extending extended BPF

> int bpf(BPF_PROG_LOAD, int prog_id, enum bpf_prog_type type, struct nlattr *prog, int len);

I'd have thought kernel devs would have learned by now and have always, always, always included an `int flags` field in any new syscall, just to avoid the otherwise eventual need for `bpf2`. Unless the `nlattr` data is expected to be sufficient?