From: patchwork-bot+netdevbpf@kernel.org
To: Yinjun Zhang <yinjun.zhang@corigine.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
andrii@kernel.org, kafai@fb.com, songliubraving@fb.com,
yhs@fb.com, john.fastabend@gmail.com, kpsingh@kernel.org,
niklas.soderlund@corigine.com, simon.horman@corigine.com
Subject: Re: [PATCH bpf] bpftool: fix the error when lookup in no-btf maps
Date: Tue, 15 Feb 2022 17:10:12 +0000 [thread overview]
Message-ID: <164494501200.23700.5378828821722678685.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <1644249625-22479-1-git-send-email-yinjun.zhang@corigine.com>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:
On Tue, 8 Feb 2022 00:00:25 +0800 you wrote:
> When reworking btf__get_from_id() in commit a19f93cfafdf the error
> handling when calling bpf_btf_get_fd_by_id() changed. Before the rework
> if bpf_btf_get_fd_by_id() failed the error would not be propagated to
> callers of btf__get_from_id(), after the rework it is. This lead to a
> change in behavior in print_key_value() that now prints an error when
> trying to lookup keys in maps with no btf available.
>
> [...]
Here is the summary with links:
- [bpf] bpftool: fix the error when lookup in no-btf maps
https://git.kernel.org/bpf/bpf-next/c/edc21dc909c6
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2022-02-15 17:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-07 16:00 [PATCH bpf] bpftool: fix the error when lookup in no-btf maps Yinjun Zhang
2022-02-07 17:42 ` Andrii Nakryiko
2022-02-07 17:57 ` Jiri Olsa
2022-02-07 18:26 ` Jiri Olsa
2022-02-07 20:34 ` Yonghong Song
2022-02-08 4:53 ` Yinjun Zhang
2022-02-15 9:47 ` Jiri Olsa
2022-02-15 17:10 ` patchwork-bot+netdevbpf [this message]
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=164494501200.23700.5378828821722678685.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=kafai@fb.com \
--cc=kpsingh@kernel.org \
--cc=niklas.soderlund@corigine.com \
--cc=simon.horman@corigine.com \
--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.