tools: bpf: don't complain about no kernel version for networking code
authorJakub Kicinski <jakub.kicinski@netronome.com>
Thu, 10 May 2018 17:24:42 +0000 (10:24 -0700)
committerDaniel Borkmann <daniel@iogearbox.net>
Thu, 10 May 2018 23:40:52 +0000 (01:40 +0200)
commit17387dd5ac2c9c4e5f7d38b5affcd70e059f0a8c
tree3eff4d0d19a8bfc59266fd2ca56fce6eeb818517
parent2eb57bb8f6769fe94f8f9865342ffa0f6c257e0a
tools: bpf: don't complain about no kernel version for networking code

BPF programs only have to specify the target kernel version for
tracing related hooks, in networking world that requirement does
not really apply.  Loosen the checks in libbpf to reflect that.

bpf_object__open() users will continue to see the error for backward
compatibility (and because prog_type is not available there).

Error code for NULL file name is changed from ENOENT to EINVAL,
as it seems more appropriate, hopefully, that's an OK change.

Signed-off-by: Jakub Kicinski <jakub.kicinski@netronome.com>
Reviewed-by: Quentin Monnet <quentin.monnet@netronome.com>
Signed-off-by: Daniel Borkmann <daniel@iogearbox.net>
tools/lib/bpf/libbpf.c