public inbox for linux-kselftest@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: KaFai Wan <mannkafai@gmail.com>
Cc: alexei.starovoitov@gmail.com, martin.lau@linux.dev,
	ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
	eddyz87@gmail.com, song@kernel.org, yonghong.song@linux.dev,
	john.fastabend@gmail.com, kpsingh@kernel.org, sdf@fomichev.me,
	haoluo@google.com, jolsa@kernel.org, davem@davemloft.net,
	edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
	horms@kernel.org, mykolal@fb.com, shuah@kernel.org,
	memxor@gmail.com, bpf@vger.kernel.org,
	linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
	linux-kselftest@vger.kernel.org, leon.hwang@linux.dev
Subject: Re: [PATCH bpf-next v4 0/2] bpf: Allow access to const void pointer arguments in tracing programs
Date: Wed, 23 Apr 2025 18:30:30 +0000	[thread overview]
Message-ID: <174543303025.2731730.15635932606525248538.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250423121329.3163461-1-mannkafai@gmail.com>

Hello:

This series was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:

On Wed, 23 Apr 2025 20:13:27 +0800 you wrote:
> If we try to access argument which is pointer to const void, it's an
> UNKNOWN type, verifier will fail to load.
> 
> Use is_void_or_int_ptr to check if type is void or int pointer.
> Add a selftest to check it.
> 
> 
> [...]

Here is the summary with links:
  - [bpf-next,v4,1/2] bpf: Allow access to const void pointer arguments in tracing programs
    https://git.kernel.org/bpf/bpf-next/c/1271a40eeafa
  - [bpf-next,v4,2/2] selftests/bpf: Add test to access const void pointer argument in tracing program
    https://git.kernel.org/bpf/bpf-next/c/4c0a42c50021

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



      parent reply	other threads:[~2025-04-23 18:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-23 12:13 [PATCH bpf-next v4 0/2] bpf: Allow access to const void pointer arguments in tracing programs KaFai Wan
2025-04-23 12:13 ` [PATCH bpf-next v4 1/2] " KaFai Wan
2025-04-23 18:27   ` Andrii Nakryiko
2025-04-23 12:13 ` [PATCH bpf-next v4 2/2] selftests/bpf: Add test to access const void pointer argument in tracing program KaFai Wan
2025-04-23 18:30 ` 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=174543303025.2731730.15635932606525248538.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=alexei.starovoitov@gmail.com \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=davem@davemloft.net \
    --cc=eddyz87@gmail.com \
    --cc=edumazet@google.com \
    --cc=haoluo@google.com \
    --cc=horms@kernel.org \
    --cc=john.fastabend@gmail.com \
    --cc=jolsa@kernel.org \
    --cc=kpsingh@kernel.org \
    --cc=kuba@kernel.org \
    --cc=leon.hwang@linux.dev \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=mannkafai@gmail.com \
    --cc=martin.lau@linux.dev \
    --cc=memxor@gmail.com \
    --cc=mykolal@fb.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=sdf@fomichev.me \
    --cc=shuah@kernel.org \
    --cc=song@kernel.org \
    --cc=yonghong.song@linux.dev \
    /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