From: Quentin Monnet <quentin@isovalent.com>
To: Michal Rostecki <mrostecki@opensuse.org>, bpf@vger.kernel.org
Cc: Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Martin KaFai Lau <kafai@fb.com>, Song Liu <songliubraving@fb.com>,
Yonghong Song <yhs@fb.com>, Andrii Nakryiko <andriin@fb.com>,
Jakub Kicinski <kuba@kernel.org>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Shuah Khan <shuah@kernel.org>,
linux-kselftest@vger.kernel.org
Subject: Re: [PATCH bpf-next v3 0/5] bpftool: Make probes which emit dmesg warnings optional
Date: Wed, 26 Feb 2020 11:17:21 +0000 [thread overview]
Message-ID: <e4929660-21ff-e394-37a0-d72b67a3770a@isovalent.com> (raw)
In-Reply-To: <20200225194446.20651-1-mrostecki@opensuse.org>
2020-02-25 20:44 UTC+0100 ~ Michal Rostecki <mrostecki@opensuse.org>
> Feature probes in bpftool related to bpf_probe_write_user and
> bpf_trace_printk helpers emit dmesg warnings which might be confusing
> for people running bpftool on production environments. This patch series
> addresses that by filtering them out by default and introducing the new
> positional argument "full" which enables all available probes.
>
> The main motivation behind those changes is ability the fact that some
> probes (for example those related to "trace" or "write_user" helpers)
> emit dmesg messages which might be confusing for people who are running
> on production environments. For details see the Cilium issue[0].
>
> v1 -> v2:
> - Do not expose regex filters to users, keep filtering logic internal,
> expose only the "full" option for including probes which emit dmesg
> warnings.
>
> v2 -> v3:
> - Do not use regex for filtering out probes, use function IDs directly.
> - Fix bash completion - in v2 only "prefix" was proposed after "macros",
> "dev" and "kernel" were not.
> - Rephrase the man page paragraph, highlight helper function names.
> - Remove tests which parse the plain output of bpftool (except the
> header/macros test), focus on testing JSON output instead.
> - Add test which compares the output with and without "full" option.
>
> [0] https://github.com/cilium/cilium/issues/10048
>
> Michal Rostecki (5):
> bpftool: Move out sections to separate functions
> bpftool: Make probes which emit dmesg warnings optional
> bpftool: Update documentation of "bpftool feature" command
> bpftool: Update bash completion for "bpftool feature" command
> selftests/bpf: Add test for "bpftool feature" command
>
> .../bpftool/Documentation/bpftool-feature.rst | 19 +-
> tools/bpf/bpftool/bash-completion/bpftool | 3 +-
> tools/bpf/bpftool/feature.c | 283 +++++++++++-------
> tools/testing/selftests/.gitignore | 5 +-
> tools/testing/selftests/bpf/Makefile | 3 +-
> tools/testing/selftests/bpf/test_bpftool.py | 179 +++++++++++
> tools/testing/selftests/bpf/test_bpftool.sh | 5 +
> 7 files changed, 374 insertions(+), 123 deletions(-)
> create mode 100644 tools/testing/selftests/bpf/test_bpftool.py
> create mode 100755 tools/testing/selftests/bpf/test_bpftool.sh
>
This version looks good to me, thanks!
Reviewed-by: Quentin Monnet <quentin@isovalent.com>
(Please keep Acked-by/Reviewed-by tags between versions if there are no
significant changes, here for patch 1.)
That's a lot of tests now that we don't have the regex and filtering is
very straightforward, but it does not hurt. I checked and they all pass
on my system.
Thanks,
Quentin
next prev parent reply other threads:[~2020-02-26 11:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-25 19:44 [PATCH bpf-next v3 0/5] bpftool: Make probes which emit dmesg warnings optional Michal Rostecki
2020-02-25 19:44 ` [PATCH bpf-next v3 1/5] bpftool: Move out sections to separate functions Michal Rostecki
2020-02-25 19:44 ` [PATCH bpf-next v3 2/5] bpftool: Make probes which emit dmesg warnings optional Michal Rostecki
2020-02-26 15:35 ` Daniel Borkmann
2020-02-25 19:44 ` [PATCH bpf-next v3 3/5] bpftool: Update documentation of "bpftool feature" command Michal Rostecki
2020-02-25 19:44 ` [PATCH bpf-next v3 4/5] bpftool: Update bash completion for " Michal Rostecki
2020-02-25 19:44 ` [PATCH bpf-next v3 5/5] selftests/bpf: Add test " Michal Rostecki
2020-02-26 15:34 ` Daniel Borkmann
2020-02-26 15:42 ` Michal Rostecki
2020-02-26 15:43 ` Quentin Monnet
2020-02-26 11:17 ` Quentin Monnet [this message]
2020-02-26 12:17 ` [PATCH bpf-next v3 0/5] bpftool: Make probes which emit dmesg warnings optional Michal Rostecki
2020-02-26 12:33 ` Quentin Monnet
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=e4929660-21ff-e394-37a0-d72b67a3770a@isovalent.com \
--to=quentin@isovalent.com \
--cc=andriin@fb.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=kafai@fb.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=mrostecki@opensuse.org \
--cc=netdev@vger.kernel.org \
--cc=shuah@kernel.org \
--cc=songliubraving@fb.com \
--cc=yhs@fb.com \
/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