From: patchwork-bot+netdevbpf@kernel.org
To: Daniel Borkmann <daniel@iogearbox.net>
Cc: ast@kernel.org, andrii@kernel.org, kongln9170@gmail.com,
memxor@gmail.com, bpf@vger.kernel.org
Subject: Re: [PATCH bpf 1/5] bpf: Add MEM_WRITE attribute
Date: Tue, 22 Oct 2024 22:50:31 +0000 [thread overview]
Message-ID: <172963743177.1101685.1294930119594864937.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241021152809.33343-1-daniel@iogearbox.net>
Hello:
This series was applied to bpf/bpf.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Mon, 21 Oct 2024 17:28:05 +0200 you wrote:
> Add a MEM_WRITE attribute for BPF helper functions which can be used in
> bpf_func_proto to annotate an argument type in order to let the verifier
> know that the helper writes into the memory passed as an argument. In
> the past MEM_UNINIT has been (ab)used for this function, but the latter
> merely tells the verifier that the passed memory can be uninitialized.
>
> There have been bugs with overloading the latter but aside from that
> there are also cases where the passed memory is read + written which
> currently cannot be expressed, see also 4b3786a6c539 ("bpf: Zero former
> ARG_PTR_TO_{LONG,INT} args in case of error").
>
> [...]
Here is the summary with links:
- [bpf,1/5] bpf: Add MEM_WRITE attribute
https://git.kernel.org/bpf/bpf/c/6fad274f06f0
- [bpf,2/5] bpf: Fix overloading of MEM_UNINIT's meaning
https://git.kernel.org/bpf/bpf/c/8ea607330a39
- [bpf,3/5] bpf: Remove MEM_UNINIT from skb/xdp MTU helpers
https://git.kernel.org/bpf/bpf/c/14a3d3ef02ba
- [bpf,4/5] selftests/bpf: Add test for writes to .rodata
https://git.kernel.org/bpf/bpf/c/baa802d2aa5c
- [bpf,5/5] selftests/bpf: Add test for passing in uninit mtu_len
https://git.kernel.org/bpf/bpf/c/82bbe133312b
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:[~2024-10-22 22:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-21 15:28 [PATCH bpf 1/5] bpf: Add MEM_WRITE attribute Daniel Borkmann
2024-10-21 15:28 ` [PATCH bpf 2/5] bpf: Fix overloading of MEM_UNINIT's meaning Daniel Borkmann
2024-10-22 0:46 ` Kumar Kartikeya Dwivedi
2024-10-21 15:28 ` [PATCH bpf 3/5] bpf: Remove MEM_UNINIT from skb/xdp MTU helpers Daniel Borkmann
2024-10-22 0:46 ` Kumar Kartikeya Dwivedi
2024-10-21 15:28 ` [PATCH bpf 4/5] selftests/bpf: Add test for writes to .rodata Daniel Borkmann
2024-10-22 0:47 ` Kumar Kartikeya Dwivedi
2024-10-21 15:28 ` [PATCH bpf 5/5] selftests/bpf: Add test for passing in uninit mtu_len Daniel Borkmann
2024-10-22 0:47 ` Kumar Kartikeya Dwivedi
2024-10-22 0:46 ` [PATCH bpf 1/5] bpf: Add MEM_WRITE attribute Kumar Kartikeya Dwivedi
2024-10-22 22:50 ` 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=172963743177.1101685.1294930119594864937.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=daniel@iogearbox.net \
--cc=kongln9170@gmail.com \
--cc=memxor@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