public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Eduard Zingerman <eddyz87@gmail.com>
To: Tao Chen <chen.dylane@linux.dev>,
	ast@kernel.org, daniel@iogearbox.net,  andrii@kernel.org,
	haoluo@google.com, jolsa@kernel.org, qmo@kernel.org
Cc: bpf@vger.kernel.org, linux-kernel@vger.kernel.org, chen.dylane@gmail.com
Subject: Re: [PATCH bpf-next v8 0/5] Add prog_kfunc feature probe
Date: Mon, 24 Feb 2025 17:28:51 -0800	[thread overview]
Message-ID: <abeaac9dadaddc3b95826eb12ee169558a271bbe.camel@gmail.com> (raw)
In-Reply-To: <c9e36bd3-0903-4ce6-afdc-7deff6d489c1@linux.dev>

On Tue, 2025-02-25 at 01:13 +0800, Tao Chen wrote:

[...]

> Hi Eduard,
> I used a simple script to find all kfunc prog types and comapre it with 
> your program, most of them are consistent， the results are as follows, 
> and i add pathch 4 additionally to fix kfunc probe like 
> bpf_session_is_return.

Hi Tao,

Thank you for putting together the python script. I double checked
output of the script and the output of the test and find these
consistent.

(I noticed that a few kfuncs are in the vmlinux.h but are not printed
 by the test:
 - bpf_skb_get_xfrm_info
 - bpf_skb_set_xfrm_info
 - bpf_xdp_get_xfrm_state
 - bpf_xdp_xfrm_state_release
 - bpf_dynptr_from_skb
 - bpf_dynptr_from_xdp
 - bpf_sock_addr_set_sun_path
 but that is another topic).

Thanks,
Eduard

[...]


      reply	other threads:[~2025-02-25  1:28 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-24 16:59 [PATCH bpf-next v8 0/5] Add prog_kfunc feature probe Tao Chen
2025-02-24 16:59 ` [PATCH bpf-next v8 1/5] libbpf: Extract prog load type check from libbpf_probe_bpf_helper Tao Chen
2025-02-24 16:59 ` [PATCH bpf-next v8 2/5] libbpf: Init fd_array when prog probe load Tao Chen
2025-02-24 16:59 ` [PATCH bpf-next v8 3/5] libbpf: Add libbpf_probe_bpf_kfunc API Tao Chen
2025-02-25  1:15   ` Andrii Nakryiko
2025-02-25  5:47     ` Tao Chen
2025-02-25 17:01       ` Andrii Nakryiko
2025-02-24 16:59 ` [PATCH bpf-next v8 4/5] libbpf: Init kprobe prog expected_attach_type for kfunc probe Tao Chen
2025-02-25  1:15   ` Andrii Nakryiko
2025-02-25  5:44     ` Tao Chen
2025-02-25 17:04       ` Andrii Nakryiko
2025-02-26 11:12         ` Jiri Olsa
2025-02-26 16:10           ` Tao Chen
2025-02-24 16:59 ` [PATCH bpf-next v8 5/5] selftests/bpf: Add libbpf_probe_bpf_kfunc API selftests Tao Chen
2025-02-24 17:13 ` [PATCH bpf-next v8 0/5] Add prog_kfunc feature probe Tao Chen
2025-02-25  1:28   ` Eduard Zingerman [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=abeaac9dadaddc3b95826eb12ee169558a271bbe.camel@gmail.com \
    --to=eddyz87@gmail.com \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=chen.dylane@gmail.com \
    --cc=chen.dylane@linux.dev \
    --cc=daniel@iogearbox.net \
    --cc=haoluo@google.com \
    --cc=jolsa@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=qmo@kernel.org \
    /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