From: patchwork-bot+netdevbpf@kernel.org
To: Kumar Kartikeya Dwivedi <memxor@gmail.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, andrii@kernel.org,
daniel@iogearbox.net, martin.lau@kernel.org,
joannelkoong@gmail.com, void@manifault.com
Subject: Re: [PATCH bpf-next v2 0/7] Dynptr refactorings
Date: Fri, 09 Dec 2022 02:50:17 +0000 [thread overview]
Message-ID: <167055421711.8327.12132622553972025169.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221207204141.308952-1-memxor@gmail.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Thu, 8 Dec 2022 02:11:34 +0530 you wrote:
> This is part 1 of https://lore.kernel.org/bpf/20221018135920.726360-1-memxor@gmail.com.
> This thread also gives some background on why the refactor is being done:
> https://lore.kernel.org/bpf/CAEf4Bzb4beTHgVo+G+jehSj8oCeAjRbRcm6MRe=Gr+cajRBwEw@mail.gmail.com
>
> As requested in patch 6 by Alexei, it only includes patches which
> refactors the code, on top of which further fixes will be made in part
> 2. The refactor itself fixes another issue as a side effect. No
> functional change is intended (except a few modified log messages).
>
> [...]
Here is the summary with links:
- [bpf-next,v2,1/7] bpf: Refactor ARG_PTR_TO_DYNPTR checks into process_dynptr_func
https://git.kernel.org/bpf/bpf-next/c/6b75bd3d0367
- [bpf-next,v2,2/7] bpf: Propagate errors from process_* checks in check_func_arg
https://git.kernel.org/bpf/bpf-next/c/ac50fe51ce87
- [bpf-next,v2,3/7] bpf: Rework process_dynptr_func
https://git.kernel.org/bpf/bpf-next/c/270605317366
- [bpf-next,v2,4/7] bpf: Rework check_func_arg_reg_off
https://git.kernel.org/bpf/bpf-next/c/184c9bdb8f65
- [bpf-next,v2,5/7] bpf: Move PTR_TO_STACK alignment check to process_dynptr_func
https://git.kernel.org/bpf/bpf-next/c/f6ee298fa140
- [bpf-next,v2,6/7] bpf: Use memmove for bpf_dynptr_{read,write}
https://git.kernel.org/bpf/bpf-next/c/76d16077bef0
- [bpf-next,v2,7/7] selftests/bpf: Add test for dynptr reinit in user_ringbuf callback
https://git.kernel.org/bpf/bpf-next/c/292064cce796
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:[~2022-12-09 2:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-07 20:41 [PATCH bpf-next v2 0/7] Dynptr refactorings Kumar Kartikeya Dwivedi
2022-12-07 20:41 ` [PATCH bpf-next v2 1/7] bpf: Refactor ARG_PTR_TO_DYNPTR checks into process_dynptr_func Kumar Kartikeya Dwivedi
2022-12-07 20:41 ` [PATCH bpf-next v2 2/7] bpf: Propagate errors from process_* checks in check_func_arg Kumar Kartikeya Dwivedi
2022-12-07 20:41 ` [PATCH bpf-next v2 3/7] bpf: Rework process_dynptr_func Kumar Kartikeya Dwivedi
2022-12-07 20:41 ` [PATCH bpf-next v2 4/7] bpf: Rework check_func_arg_reg_off Kumar Kartikeya Dwivedi
2022-12-09 2:47 ` Alexei Starovoitov
2022-12-07 20:41 ` [PATCH bpf-next v2 5/7] bpf: Move PTR_TO_STACK alignment check to process_dynptr_func Kumar Kartikeya Dwivedi
2022-12-07 20:41 ` [PATCH bpf-next v2 6/7] bpf: Use memmove for bpf_dynptr_{read,write} Kumar Kartikeya Dwivedi
2022-12-07 20:41 ` [PATCH bpf-next v2 7/7] selftests/bpf: Add test for dynptr reinit in user_ringbuf callback Kumar Kartikeya Dwivedi
2022-12-09 2: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=167055421711.8327.12132622553972025169.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=joannelkoong@gmail.com \
--cc=martin.lau@kernel.org \
--cc=memxor@gmail.com \
--cc=void@manifault.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