From: patchwork-bot+netdevbpf@kernel.org
To: Daniel Rosenberg <drosen@google.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
john.fastabend@gmail.com, andrii@kernel.org,
martin.lau@linux.dev, song@kernel.org, yhs@fb.com,
kpsingh@kernel.org, sdf@google.com, haoluo@google.com,
jolsa@kernel.org, shuah@kernel.org, corbet@lwn.net,
joannelkoong@gmail.com, mykolal@fb.com,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
kernel-team@android.com
Subject: Re: [PATCH bpf-next v3 0/5] Dynptr Verifier Adjustments
Date: Sun, 07 May 2023 00:00:20 +0000 [thread overview]
Message-ID: <168341762073.15595.436910654395923794.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230506013134.2492210-1-drosen@google.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Fri, 5 May 2023 18:31:29 -0700 you wrote:
> These patches relax a few verifier requirements around dynptrs.
> Patches 1-3 are unchanged from v2, apart from rebasing
> Patch 4 is the same as in v1, see
> https://lore.kernel.org/bpf/CA+PiJmST4WUH061KaxJ4kRL=fqy3X6+Wgb2E2rrLT5OYjUzxfQ@mail.gmail.com/
> Patch 5 adds a test for the change in Patch 4
>
> Daniel Rosenberg (5):
> bpf: Allow NULL buffers in bpf_dynptr_slice(_rw)
> selftests/bpf: Test allowing NULL buffer in dynptr slice
> selftests/bpf: Check overflow in optional buffer
> bpf: verifier: Accept dynptr mem as mem in helpers
> selftests/bpf: Accept mem from dynptr in helper funcs
>
> [...]
Here is the summary with links:
- [bpf-next,v3,1/5] bpf: Allow NULL buffers in bpf_dynptr_slice(_rw)
https://git.kernel.org/bpf/bpf-next/c/3bda08b63670
- [bpf-next,v3,2/5] selftests/bpf: Test allowing NULL buffer in dynptr slice
https://git.kernel.org/bpf/bpf-next/c/1ce33b6c846f
- [bpf-next,v3,3/5] selftests/bpf: Check overflow in optional buffer
https://git.kernel.org/bpf/bpf-next/c/3881fdfed21f
- [bpf-next,v3,4/5] bpf: verifier: Accept dynptr mem as mem in helpers
https://git.kernel.org/bpf/bpf-next/c/2012c867c800
- [bpf-next,v3,5/5] selftests/bpf: Accept mem from dynptr in helper funcs
https://git.kernel.org/bpf/bpf-next/c/798e48fc28fa
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:[~2023-05-07 0:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-06 1:31 [PATCH bpf-next v3 0/5] Dynptr Verifier Adjustments Daniel Rosenberg
2023-05-06 1:31 ` [PATCH bpf-next v3 1/5] bpf: Allow NULL buffers in bpf_dynptr_slice(_rw) Daniel Rosenberg
2023-05-06 1:31 ` [PATCH bpf-next v3 2/5] selftests/bpf: Test allowing NULL buffer in dynptr slice Daniel Rosenberg
2023-05-06 1:31 ` [PATCH bpf-next v3 3/5] selftests/bpf: Check overflow in optional buffer Daniel Rosenberg
2023-05-06 1:31 ` [PATCH bpf-next v3 4/5] bpf: verifier: Accept dynptr mem as mem in helpers Daniel Rosenberg
2023-05-06 1:31 ` [PATCH bpf-next v3 5/5] selftests/bpf: Accept mem from dynptr in helper funcs Daniel Rosenberg
2023-05-07 0:00 ` 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=168341762073.15595.436910654395923794.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=corbet@lwn.net \
--cc=daniel@iogearbox.net \
--cc=drosen@google.com \
--cc=haoluo@google.com \
--cc=joannelkoong@gmail.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kernel-team@android.com \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=mykolal@fb.com \
--cc=sdf@google.com \
--cc=shuah@kernel.org \
--cc=song@kernel.org \
--cc=yhs@fb.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