Benjamin Poirier 0478c3bf81 bpftool: Use print_entry_error() in case of ENOENT when dumping ... Commit bf598a8f0f ("bpftool: Improve handling of ENOENT on map dumps") used print_entry_plain() in case of ENOENT. However, that commit introduces dead code. Per-cpu maps are zero-filled. When reading them, it's all or nothing. There will never be a case where some cpus have an entry and others don't. The truth is that ENOENT is an error case. Use print_entry_error() to output the desired message. That function's "value" parameter is also renamed to indicate that we never use it for an actual map value. The output format is unchanged. Signed-off-by: Benjamin Poirier <bpoirier@suse.com> Reviewed-by: Quentin Monnet <quentin.monnet@netronome.com> Reviewed-by: Jakub Kicinski <jakub.kicinski@netronome.com> Signed-off-by: Daniel Borkmann <daniel@iogearbox.net>		2019-04-16 10:16:33 +02:00
..
bpftool	bpftool: Use print_entry_error() in case of ENOENT when dumping	2019-04-16 10:16:33 +02:00
.gitignore	tools/bpftool: ignore build products	2018-07-26 02:50:26 +02:00
bpf_asm.c
bpf_dbg.c	bpf: fix uninitialized variable in bpf tools	2018-04-26 22:23:02 +02:00
bpf_exp.l	bpf: fix cbpf parser bug for octal numbers	2018-06-03 07:46:55 -07:00
bpf_exp.y
bpf_jit_disasm.c	tools/bpf_jit_disasm: silence a static checker warning	2018-01-18 22:15:37 +01:00
Makefile	bpf: fix for lex/yacc build error with gcc-5	2018-04-25 23:27:46 +02:00
Makefile.helpers	tools: bpf: build and install man page for eBPF helpers from bpftool/	2018-07-12 18:55:53 +02:00