From: patchwork-bot+netdevbpf@kernel.org
To: Jiri Olsa <jolsa@kernel.org>
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
yinjun.zhang@corigine.com, netdev@vger.kernel.org,
bpf@vger.kernel.org, kafai@fb.com, songliubraving@fb.com,
yhs@fb.com, john.fastabend@gmail.com, kpsingh@chromium.org
Subject: Re: [PATCH bpf-next] bpftool: Fix pretty print dump for maps without BTF loaded
Date: Wed, 16 Feb 2022 18:40:09 +0000 [thread overview]
Message-ID: <164503680959.7965.12987975510885594675.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220216092102.125448-1-jolsa@kernel.org>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:
On Wed, 16 Feb 2022 10:21:02 +0100 you wrote:
> The commit e5043894b21f ("bpftool: Use libbpf_get_error() to check error")
> fails to dump map without BTF loaded in pretty mode (-p option).
>
> Fixing this by making sure get_map_kv_btf won't fail in case there's
> no BTF available for the map.
>
> Cc: Yinjun Zhang <yinjun.zhang@corigine.com>
> Fixes: e5043894b21f ("bpftool: Use libbpf_get_error() to check error")
> Suggested-by: Andrii Nakryiko <andrii@kernel.org>
> Signed-off-by: Jiri Olsa <jolsa@kernel.org>
>
> [...]
Here is the summary with links:
- [bpf-next] bpftool: Fix pretty print dump for maps without BTF loaded
https://git.kernel.org/bpf/bpf-next/c/2e3f7bed2837
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2022-02-16 18:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-16 9:21 [PATCH bpf-next] bpftool: Fix pretty print dump for maps without BTF loaded Jiri Olsa
2022-02-16 18:40 ` patchwork-bot+netdevbpf [this message]
2022-02-16 23:08 ` 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=164503680959.7965.12987975510885594675.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kafai@fb.com \
--cc=kpsingh@chromium.org \
--cc=netdev@vger.kernel.org \
--cc=songliubraving@fb.com \
--cc=yhs@fb.com \
--cc=yinjun.zhang@corigine.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.