diff options
| author | Quentin Monnet <[email protected]> | 2019-05-24 10:36:47 +0000 |
|---|---|---|
| committer | Daniel Borkmann <[email protected]> | 2019-05-28 09:03:26 +0000 |
| commit | 60276f9849988d3d3a54943c9ec27222c5819dae (patch) | |
| tree | 8da64a5ab5620886f7e3d1c88f877f44828e3720 /tools/bpf/bpftool/prog.c | |
| parent | tools: bpftool: add -d option to get debug output from libbpf (diff) | |
| download | kernel-60276f9849988d3d3a54943c9ec27222c5819dae.tar.gz kernel-60276f9849988d3d3a54943c9ec27222c5819dae.zip | |
libbpf: add bpf_object__load_xattr() API function to pass log_level
libbpf was recently made aware of the log_level attribute for programs,
used to specify the level of information expected to be dumped by the
verifier. Function bpf_prog_load_xattr() got support for this log_level
parameter.
But some applications using libbpf rely on another function to load
programs, bpf_object__load(), which does accept any parameter for log
level. Create an API function based on bpf_object__load(), but accepting
an "attr" object as a parameter. Then add a log_level field to that
object, so that applications calling the new bpf_object__load_xattr()
can pick the desired log level.
v3:
- Rewrite commit log.
v2:
- We are in a new cycle, bump libbpf extraversion number.
Signed-off-by: Quentin Monnet <[email protected]>
Reviewed-by: Jakub Kicinski <[email protected]>
Signed-off-by: Daniel Borkmann <[email protected]>
Diffstat (limited to 'tools/bpf/bpftool/prog.c')
0 files changed, 0 insertions, 0 deletions
