From: Alan Maguire <alan.maguire@oracle.com>
To: "Masami Hiramatsu (Google)" <mhiramat@kernel.org>,
linux-trace-kernel@vger.kernel.org
Cc: linux-kernel@vger.kernel.org,
Steven Rostedt <rostedt@goodmis.org>,
Martin KaFai Lau <martin.lau@linux.dev>,
bpf@vger.kernel.org, Sven Schnelle <svens@linux.ibm.com>,
Alexei Starovoitov <ast@kernel.org>
Subject: Re: [PATCH v2 3/9] bpf/btf: Add a function to search a member of a struct/union
Date: Thu, 20 Jul 2023 23:34:42 +0100 [thread overview]
Message-ID: <dbb5500e-f623-77fb-2606-c3073371e979@oracle.com> (raw)
In-Reply-To: <168960742712.34107.9849785489776347376.stgit@devnote2>
On 17/07/2023 16:23, Masami Hiramatsu (Google) wrote:
> From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
>
> Add btf_find_struct_member() API to search a member of a given data structure
> or union from the member's name.
>
> Signed-off-by: Masami Hiramatsu (Google) <mhiramat@kernel.org>
A few small things below, but
Reviewed-by: Alan Maguire <alan.maguire@oracle.com>
> ---
> include/linux/btf.h | 3 +++
> kernel/bpf/btf.c | 38 ++++++++++++++++++++++++++++++++++++++
> 2 files changed, 41 insertions(+)
>
> diff --git a/include/linux/btf.h b/include/linux/btf.h
> index 98fbbcdd72ec..097fe9b51562 100644
> --- a/include/linux/btf.h
> +++ b/include/linux/btf.h
> @@ -225,6 +225,9 @@ const struct btf_type *btf_find_func_proto(struct btf *btf,
> const char *func_name);
> const struct btf_param *btf_get_func_param(const struct btf_type *func_proto,
> s32 *nr);
> +const struct btf_member *btf_find_struct_member(struct btf *btf,
> + const struct btf_type *type,
> + const char *member_name);
>
> #define for_each_member(i, struct_type, member) \
> for (i = 0, member = btf_type_member(struct_type); \
> diff --git a/kernel/bpf/btf.c b/kernel/bpf/btf.c
> index e015b52956cb..452ffb0393d6 100644
> --- a/kernel/bpf/btf.c
> +++ b/kernel/bpf/btf.c
> @@ -1992,6 +1992,44 @@ const struct btf_param *btf_get_func_param(const struct btf_type *func_proto, s3
> return NULL;
> }
>
> +/*
> + * Find a member of data structure/union by name and return it.
> + * Return NULL if not found, or -EINVAL if parameter is invalid.
> + */
> +const struct btf_member *btf_find_struct_member(struct btf *btf,
> + const struct btf_type *type,
> + const char *member_name)
> +{
> + const struct btf_member *members, *ret;
> + const char *name;
> + int i, vlen;
> +
> + if (!btf || !member_name || !btf_type_is_struct(type))
> + return ERR_PTR(-EINVAL);
> +
> + vlen = btf_type_vlen(type);
> + members = (const struct btf_member *)(type + 1);
> +
> + for (i = 0; i < vlen; i++) {
could use for_each_member() here I think, or perhaps use
btf_type_member(type) when getting member pointer above.
> + if (!members[i].name_off) {
> + /* unnamed union: dig deeper */
> + type = btf_type_by_id(btf, members[i].type);
> + if (!IS_ERR_OR_NULL(type)) {
> + ret = btf_find_struct_member(btf, type,
> + member_name);
You'll need to skip modifiers before calling btf_find_struct_member()
here I think; it's possible to have a const anonymous union for example,
so to get to the union you'd need to skip the modifiers first. Otherwise
you could fail the btf_type_is_struct() test on re-entry.
> + if (!IS_ERR_OR_NULL(ret))
> + return ret;
> + }
> + } else {
> + name = btf_name_by_offset(btf, members[i].name_off);
> + if (name && !strcmp(member_name, name))
> + return &members[i];
> + }
> + }
> +
> + return NULL;
> +}
> +
> static u32 btf_resolved_type_id(const struct btf *btf, u32 type_id)
> {
> while (type_id < btf->start_id)
>
>
next prev parent reply other threads:[~2023-07-20 22:35 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-17 15:23 [PATCH v2 0/9] tracing: Improbe BTF support on probe events Masami Hiramatsu (Google)
2023-07-17 15:23 ` [PATCH v2 1/9] tracing/probes: Fix to add NULL check for BTF APIs Masami Hiramatsu (Google)
2023-07-17 15:23 ` [PATCH v2 2/9] bpf/btf: tracing: Move finding func-proto API and getting func-param API to BTF Masami Hiramatsu (Google)
2023-07-17 18:39 ` Steven Rostedt
2023-07-17 23:46 ` Masami Hiramatsu
2023-07-17 23:51 ` Alexei Starovoitov
2023-07-18 1:03 ` Masami Hiramatsu
2023-07-17 23:51 ` Steven Rostedt
2023-07-18 1:02 ` Masami Hiramatsu
2023-07-18 2:40 ` Donglin Peng
2023-07-18 10:44 ` Masami Hiramatsu
2023-07-18 13:56 ` Masami Hiramatsu
2023-07-18 17:11 ` Alexei Starovoitov
2023-07-18 23:03 ` Masami Hiramatsu
2023-07-18 23:12 ` Alexei Starovoitov
2023-07-19 15:17 ` Masami Hiramatsu
2023-07-19 2:09 ` Donglin Peng
2023-07-19 15:15 ` Masami Hiramatsu
2023-07-19 12:36 ` Alan Maguire
2023-07-19 15:24 ` Masami Hiramatsu
2023-07-19 15:49 ` Alan Maguire
2023-07-17 15:23 ` [PATCH v2 3/9] bpf/btf: Add a function to search a member of a struct/union Masami Hiramatsu (Google)
2023-07-20 22:34 ` Alan Maguire [this message]
2023-07-21 14:22 ` Masami Hiramatsu
2023-07-17 15:23 ` [PATCH v2 4/9] tracing/probes: Support BTF based data structure field access Masami Hiramatsu (Google)
2023-07-20 22:51 ` Alan Maguire
2023-07-21 14:22 ` Masami Hiramatsu
2023-07-17 15:24 ` [PATCH v2 5/9] tracing/probes: Support BTF field access from $retval Masami Hiramatsu (Google)
2023-07-17 15:24 ` [PATCH v2 6/9] tracing/probes: Add string type check with BTF Masami Hiramatsu (Google)
2023-07-17 15:24 ` [PATCH v2 7/9] tracing/fprobe-event: Assume fprobe is a return event by $retval Masami Hiramatsu (Google)
2023-07-17 15:24 ` [PATCH v2 8/9] selftests/ftrace: Add BTF fields access testcases Masami Hiramatsu (Google)
2023-07-20 23:00 ` Alan Maguire
2023-07-21 1:42 ` Masami Hiramatsu
2023-07-17 15:24 ` [PATCH v2 9/9] Documentation: tracing: Update fprobe event example with BTF field Masami Hiramatsu (Google)
2023-07-20 22:53 ` Alan Maguire
2023-07-21 13:58 ` Masami Hiramatsu
2023-07-19 9:02 ` [PATCH v2 0/9] tracing: Improbe BTF support on probe events Alan Maguire
2023-07-19 16:01 ` Masami Hiramatsu
2023-07-20 21:50 ` Alan Maguire
2023-07-25 23:45 ` Masami Hiramatsu
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=dbb5500e-f623-77fb-2606-c3073371e979@oracle.com \
--to=alan.maguire@oracle.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=mhiramat@kernel.org \
--cc=rostedt@goodmis.org \
--cc=svens@linux.ibm.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;
as well as URLs for NNTP newsgroup(s).