BPF List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: JP Kobryn <inwardvessel@gmail.com>
Cc: andrii@kernel.org, ast@kernel.org, eddyz87@gmail.com,
	bpf@vger.kernel.org
Subject: Re: [PATCH bpf-next v3 0/2] allow kfuncs in tracepoint and perf event
Date: Fri, 06 Sep 2024 00:10:34 +0000	[thread overview]
Message-ID: <172558143499.1881463.2654494687672084301.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240905223812.141857-1-inwardvessel@gmail.com>

Hello:

This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:

On Thu,  5 Sep 2024 15:38:10 -0700 you wrote:
> It is possible to call a cpumask kfunc within a raw tp_btf program but not
> possible within tracepoint or perf event programs. Currently, the verifier
> receives -EACCESS from fetch_kfunc_meta() as a result of not finding any
> kfunc hook associated with these program types.
> 
> This patch series associates tracepoint and perf event program types with
> the tracing hook and includes test coverage.
> 
> [...]

Here is the summary with links:
  - [bpf-next,v3,1/2] bpf: allow kfuncs within tracepoint and perf event programs
    https://git.kernel.org/bpf/bpf-next/c/bc638d8cb5be
  - [bpf-next,v3,2/2] bpf/selftests: coverage for tp and perf event progs using kfuncs
    https://git.kernel.org/bpf/bpf-next/c/1b3bc648f506

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2024-09-06  0:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-05 22:38 [PATCH bpf-next v3 0/2] allow kfuncs in tracepoint and perf event JP Kobryn
2024-09-05 22:38 ` [PATCH bpf-next v3 1/2] bpf: allow kfuncs within tracepoint and perf event programs JP Kobryn
2024-09-05 22:38 ` [PATCH bpf-next v3 2/2] bpf/selftests: coverage for tp and perf event progs using kfuncs JP Kobryn
2024-09-06  0: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=172558143499.1881463.2654494687672084301.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=eddyz87@gmail.com \
    --cc=inwardvessel@gmail.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