From: patchwork-bot+netdevbpf@kernel•org
To: Zesen Liu <ftyghome@gmail•com>
Cc: ast@kernel•org, daniel@iogearbox•net, andrii@kernel•org,
martin.lau@linux•dev, 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, mattbobrowski@google•com, rostedt@goodmis•org,
mhiramat@kernel•org, mathieu.desnoyers@efficios•com,
davem@davemloft•net, edumazet@google•com, kuba@kernel•org,
pabeni@redhat•com, horms@kernel•org, dxu@dxuuu•xyz,
bpf@vger•kernel.org, linux-kernel@vger•kernel.org,
linux-trace-kernel@vger•kernel.org, netdev@vger•kernel.org,
electronlsr@gmail•com, gplhust955@gmail•com,
haoran.ni.cs@gmail•com
Subject: Re: [PATCH bpf-next v3 0/2] bpf: Fix memory access flags in helper prototypes
Date: Wed, 21 Jan 2026 01:20:08 +0000 [thread overview]
Message-ID: <176895840810.676405.3513205876401603776.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260120-helper_proto-v3-0-27b0180b4e77@gmail.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel•org>:
On Tue, 20 Jan 2026 16:28:45 +0800 you wrote:
> Hi,
>
> This series adds missing memory access flags (MEM_RDONLY or MEM_WRITE) to
> several bpf helper function prototypes that use ARG_PTR_TO_MEM but lack the
> correct flag. It also adds a new check in verifier to ensure the flag is
> specified.
>
> [...]
Here is the summary with links:
- [bpf-next,v3,1/2] bpf: Fix memory access flags in helper prototypes
https://git.kernel.org/bpf/bpf-next/c/802eef5afb18
- [bpf-next,v3,2/2] bpf: Require ARG_PTR_TO_MEM with memory flag
https://git.kernel.org/bpf/bpf-next/c/ed4724212f6f
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-01-21 1:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-20 8:28 [PATCH bpf-next v3 0/2] bpf: Fix memory access flags in helper prototypes Zesen Liu
2026-01-20 8:28 ` [PATCH bpf-next v3 1/2] " Zesen Liu
2026-01-20 17:56 ` Eduard Zingerman
2026-01-20 8:28 ` [PATCH bpf-next v3 2/2] bpf: Require ARG_PTR_TO_MEM with memory flag Zesen Liu
2026-01-20 18:06 ` Eduard Zingerman
2026-01-21 1:20 ` 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=176895840810.676405.3513205876401603776.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel$(echo .)org \
--cc=andrii@kernel$(echo .)org \
--cc=ast@kernel$(echo .)org \
--cc=bpf@vger$(echo .)kernel.org \
--cc=daniel@iogearbox$(echo .)net \
--cc=davem@davemloft$(echo .)net \
--cc=dxu@dxuuu$(echo .)xyz \
--cc=eddyz87@gmail$(echo .)com \
--cc=edumazet@google$(echo .)com \
--cc=electronlsr@gmail$(echo .)com \
--cc=ftyghome@gmail$(echo .)com \
--cc=gplhust955@gmail$(echo .)com \
--cc=haoluo@google$(echo .)com \
--cc=haoran.ni.cs@gmail$(echo .)com \
--cc=horms@kernel$(echo .)org \
--cc=john.fastabend@gmail$(echo .)com \
--cc=jolsa@kernel$(echo .)org \
--cc=kpsingh@kernel$(echo .)org \
--cc=kuba@kernel$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-trace-kernel@vger$(echo .)kernel.org \
--cc=martin.lau@linux$(echo .)dev \
--cc=mathieu.desnoyers@efficios$(echo .)com \
--cc=mattbobrowski@google$(echo .)com \
--cc=mhiramat@kernel$(echo .)org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
--cc=rostedt@goodmis$(echo .)org \
--cc=sdf@fomichev$(echo .)me \
--cc=song@kernel$(echo .)org \
--cc=yonghong.song@linux$(echo .)dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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