From: Andrii Nakryiko <andriin@fb.com>
To: <bpf@vger.kernel.org>, <netdev@vger.kernel.org>, <ast@fb.com>,
<daniel@iogearbox.net>
Cc: <andrii.nakryiko@gmail.com>, <kernel-team@fb.com>,
Andrii Nakryiko <andriin@fb.com>
Subject: [PATCH v2 bpf-next 09/15] libbpf: reduce log level of supported section names dump
Date: Thu, 12 Dec 2019 08:41:22 -0800 [thread overview]
Message-ID: <20191212164129.494329-10-andriin@fb.com> (raw)
In-Reply-To: <20191212164129.494329-1-andriin@fb.com>
It's quite spammy. And now that bpf_object__open() is trying to determine
program type from its section name, we are getting these verbose messages all
the time. Reduce their log level to DEBUG.
Acked-by: Martin KaFai Lau <kafai@fb.com>
Signed-off-by: Andrii Nakryiko <andriin@fb.com>
---
tools/lib/bpf/libbpf.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/lib/bpf/libbpf.c b/tools/lib/bpf/libbpf.c
index f4a3ed73c9f5..a4cce8f1e6b1 100644
--- a/tools/lib/bpf/libbpf.c
+++ b/tools/lib/bpf/libbpf.c
@@ -5191,7 +5191,7 @@ int libbpf_prog_type_by_name(const char *name, enum bpf_prog_type *prog_type,
pr_warn("failed to guess program type from ELF section '%s'\n", name);
type_names = libbpf_get_type_names(false);
if (type_names != NULL) {
- pr_info("supported section(type) names are:%s\n", type_names);
+ pr_debug("supported section(type) names are:%s\n", type_names);
free(type_names);
}
--
2.17.1
next prev parent reply other threads:[~2019-12-12 17:03 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-12 16:41 [PATCH v2 bpf-next 00/15] Add code-generated BPF object skeleton support Andrii Nakryiko
2019-12-12 16:41 ` [PATCH v2 bpf-next 01/15] libbpf: don't require root for bpf_object__open() Andrii Nakryiko
2019-12-12 16:41 ` [PATCH v2 bpf-next 02/15] libbpf: add generic bpf_program__attach() Andrii Nakryiko
2019-12-12 16:41 ` [PATCH v2 bpf-next 03/15] libbpf: move non-public APIs from libbpf.h to libbpf_internal.h Andrii Nakryiko
2019-12-12 16:41 ` [PATCH v2 bpf-next 04/15] libbpf: add BPF_EMBED_OBJ macro for embedding BPF .o files Andrii Nakryiko
2019-12-12 16:41 ` [PATCH v2 bpf-next 05/15] libbpf: expose field/var declaration emitting API internally Andrii Nakryiko
2019-12-12 16:41 ` [PATCH v2 bpf-next 06/15] libbpf: expose BPF program's function name Andrii Nakryiko
2019-12-12 16:41 ` [PATCH v2 bpf-next 07/15] libbpf: refactor global data map initialization Andrii Nakryiko
2019-12-12 16:41 ` [PATCH v2 bpf-next 08/15] libbpf: postpone BTF ID finding for TRACING programs to load phase Andrii Nakryiko
2019-12-12 16:41 ` Andrii Nakryiko [this message]
2019-12-12 16:41 ` [PATCH v2 bpf-next 10/15] libbpf: add experimental BPF object skeleton support Andrii Nakryiko
2019-12-12 16:41 ` [PATCH v2 bpf-next 11/15] bpftool: add skeleton codegen command Andrii Nakryiko
2019-12-12 16:41 ` [PATCH v2 bpf-next 12/15] selftests/bpf: add BPF skeletons selftests and convert attach_probe.c Andrii Nakryiko
2019-12-12 16:41 ` [PATCH v2 bpf-next 13/15] selftests/bpf: convert few more selftest to skeletons Andrii Nakryiko
2019-12-12 16:41 ` [PATCH v2 bpf-next 14/15] selftests/bpf: add test validating data section to struct convertion layout Andrii Nakryiko
2019-12-12 16:41 ` [PATCH v2 bpf-next 15/15] bpftool: add `gen skeleton` BASH completions Andrii Nakryiko
2019-12-12 21:12 ` Quentin Monnet
2019-12-12 21:49 ` Andrii Nakryiko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20191212164129.494329-10-andriin@fb.com \
--to=andriin@fb.com \
--cc=andrii.nakryiko@gmail.com \
--cc=ast@fb.com \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=kernel-team@fb.com \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).