netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Martin KaFai Lau <martin.lau@linux.dev>
To: "D. Wythe" <alibuda@linux.alibaba.com>
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
	pabeni@redhat.com, song@kernel.org, sdf@google.com,
	haoluo@google.com, yhs@fb.com, edumazet@google.com,
	john.fastabend@gmail.com, kpsingh@kernel.org, jolsa@kernel.org,
	mjambigi@linux.ibm.com, wenjia@linux.ibm.com,
	wintera@linux.ibm.com, dust.li@linux.alibaba.com,
	tonylu@linux.alibaba.com, guwen@linux.alibaba.com,
	bpf@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
	netdev@vger.kernel.org, sidraya@linux.ibm.com,
	jaka@linux.ibm.com
Subject: Re: [PATCH bpf-next] libbpf: fix error when st-prefix_ops and ops from differ btf
Date: Fri, 26 Sep 2025 09:53:33 -0700	[thread overview]
Message-ID: <bf53fe2d-366f-46eb-bd9c-5820ebd87db7@linux.dev> (raw)
In-Reply-To: <20250926071751.108293-1-alibuda@linux.alibaba.com>

On 9/26/25 12:17 AM, D. Wythe wrote:
> When a module registers a struct_ops, the struct_ops type and its
> corresponding map_value type ("bpf_struct_ops_") may reside in different
> btf objects, here are four possible case:
> 
> +--------+---------------+-------------+---------------------------------+
> |        |bpf_struct_ops_| xxx_ops     |                                 |
> +--------+---------------+-------------+---------------------------------+
> | case 0 | btf_vmlinux   | bft_vmlinux | be used and reg only in vmlinux |

s/bft/btf/

> +--------+---------------+-------------+---------------------------------+
> | case 1 | btf_vmlinux   | mod_btf     | INVALID                         |
> +--------+---------------+-------------+---------------------------------+
> | case 2 | mod_btf       | btf_vmlinux | reg in mod but be used both in  |
> |        |               |             | vmlinux and mod.                |
> +--------+---------------+-------------+---------------------------------+
> | case 3 | mod_btf       | mod_btf     | be used and reg only in mod     |
> +--------+---------------+-------------+---------------------------------+
> 
> Currently we figure out the mod_btf by searching with the struct_ops type,
> which makes it impossible to figure out the mod_btf when the struct_ops
> type is in btf_vmlinux while it's corresponding map_value type is in
> mod_btf (case 2).
> 
> The fix is to use the corresponding map_value type ("bpf_struct_ops_")
> as the lookup anchor instead of the struct_ops type to figure out the
> `btf` and `mod_btf` via find_ksym_btf_id(), and then we can locate
> the kern_type_id via btf__find_by_name_kind() with the `btf` we just
> obtained from find_ksym_btf_id().
> 
> With this change the lookup obtains the correct btf and mod_btf for case 2,
> preserves correct behavior for other valid cases, and still fails as
> expected for the invalid scenario (case 1).
> 
> Fixes: 590a00888250 ("bpf: libbpf: Add STRUCT_OPS support")
> Signed-off-by: D. Wythe <alibuda@linux.alibaba.com>
> Acked-by: Andrii Nakryiko <andrii@kernel.org>
> ---
>   tools/lib/bpf/libbpf.c | 37 ++++++++++++++++++-------------------
>   1 file changed, 18 insertions(+), 19 deletions(-)
> 
> diff --git a/tools/lib/bpf/libbpf.c b/tools/lib/bpf/libbpf.c
> index 5161c2b39875..a93eed660404 100644
> --- a/tools/lib/bpf/libbpf.c
> +++ b/tools/lib/bpf/libbpf.c
> @@ -1018,35 +1018,34 @@ find_struct_ops_kern_types(struct bpf_object *obj, const char *tname_raw,
>   	const struct btf_member *kern_data_member;
>   	struct btf *btf = NULL;
>   	__s32 kern_vtype_id, kern_type_id;
> -	char tname[256];
> +	char tname[256], stname[256];
>   	__u32 i;
>   
>   	snprintf(tname, sizeof(tname), "%.*s",
>   		 (int)bpf_core_essential_name_len(tname_raw), tname_raw);
>   
> -	kern_type_id = find_ksym_btf_id(obj, tname, BTF_KIND_STRUCT,
> -					&btf, mod_btf);
> -	if (kern_type_id < 0) {
> -		pr_warn("struct_ops init_kern: struct %s is not found in kernel BTF\n",
> -			tname);
> -		return kern_type_id;
> -	}
> -	kern_type = btf__type_by_id(btf, kern_type_id);
> +	snprintf(stname, sizeof(stname), "%s%.*s", STRUCT_OPS_VALUE_PREFIX,
> +		 (int)strlen(tname), tname);

nit. strlen(tname) should not be needed. Others lgtm.

Acked-by: Martin KaFai Lau <martin.lau@kernel.org>



  reply	other threads:[~2025-09-26 16:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-26  7:17 [PATCH bpf-next] libbpf: fix error when st-prefix_ops and ops from differ btf D. Wythe
2025-09-26 16:53 ` Martin KaFai Lau [this message]
2025-09-26 20:12   ` 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=bf53fe2d-366f-46eb-bd9c-5820ebd87db7@linux.dev \
    --to=martin.lau@linux.dev \
    --cc=alibuda@linux.alibaba.com \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=davem@davemloft.net \
    --cc=dust.li@linux.alibaba.com \
    --cc=edumazet@google.com \
    --cc=guwen@linux.alibaba.com \
    --cc=haoluo@google.com \
    --cc=jaka@linux.ibm.com \
    --cc=john.fastabend@gmail.com \
    --cc=jolsa@kernel.org \
    --cc=kpsingh@kernel.org \
    --cc=kuba@kernel.org \
    --cc=mjambigi@linux.ibm.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=sdf@google.com \
    --cc=sidraya@linux.ibm.com \
    --cc=song@kernel.org \
    --cc=tonylu@linux.alibaba.com \
    --cc=wenjia@linux.ibm.com \
    --cc=wintera@linux.ibm.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;
as well as URLs for NNTP newsgroup(s).