From: patchwork-bot+netdevbpf@kernel.org
To: Dave Marchevsky <davemarchevsky@fb.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
andrii@kernel.org, martin.lau@kernel.org, kernel-team@fb.com
Subject: Re: [PATCH v2 bpf-next 0/9] Shared ownership for local kptrs
Date: Sun, 16 Apr 2023 00:50:19 +0000 [thread overview]
Message-ID: <168160621950.14536.17272966925999064717.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230415201811.343116-1-davemarchevsky@fb.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Sat, 15 Apr 2023 13:18:02 -0700 you wrote:
> This series adds support for refcounted local kptrs to the verifier. A local
> kptr is 'refcounted' if its type contains a struct bpf_refcount field:
>
> struct refcounted_node {
> long data;
> struct bpf_list_node ll;
> struct bpf_refcount ref;
> };
>
> [...]
Here is the summary with links:
- [v2,bpf-next,1/9] bpf: Remove btf_field_offs, use btf_record's fields instead
https://git.kernel.org/bpf/bpf-next/c/cd2a8079014a
- [v2,bpf-next,2/9] bpf: Introduce opaque bpf_refcount struct and add btf_record plumbing
https://git.kernel.org/bpf/bpf-next/c/d54730b50bae
- [v2,bpf-next,3/9] bpf: Support refcounted local kptrs in existing semantics
https://git.kernel.org/bpf/bpf-next/c/1512217c47f0
- [v2,bpf-next,4/9] bpf: Add bpf_refcount_acquire kfunc
https://git.kernel.org/bpf/bpf-next/c/7c50b1cb76ac
- [v2,bpf-next,5/9] bpf: Migrate bpf_rbtree_add and bpf_list_push_{front,back} to possibly fail
https://git.kernel.org/bpf/bpf-next/c/d2dcc67df910
- [v2,bpf-next,6/9] selftests/bpf: Modify linked_list tests to work with macro-ified inserts
https://git.kernel.org/bpf/bpf-next/c/de67ba3968fa
- [v2,bpf-next,7/9] bpf: Migrate bpf_rbtree_remove to possibly fail
https://git.kernel.org/bpf/bpf-next/c/404ad75a36fb
- [v2,bpf-next,8/9] bpf: Centralize btf_field-specific initialization logic
https://git.kernel.org/bpf/bpf-next/c/3e81740a9062
- [v2,bpf-next,9/9] selftests/bpf: Add refcounted_kptr tests
https://git.kernel.org/bpf/bpf-next/c/6147f15131e2
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2023-04-16 0:50 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-15 20:18 [PATCH v2 bpf-next 0/9] Shared ownership for local kptrs Dave Marchevsky
2023-04-15 20:18 ` [PATCH v2 bpf-next 1/9] bpf: Remove btf_field_offs, use btf_record's fields instead Dave Marchevsky
2023-04-15 20:18 ` [PATCH v2 bpf-next 2/9] bpf: Introduce opaque bpf_refcount struct and add btf_record plumbing Dave Marchevsky
2023-04-15 20:18 ` [PATCH v2 bpf-next 3/9] bpf: Support refcounted local kptrs in existing semantics Dave Marchevsky
2023-04-15 20:18 ` [PATCH v2 bpf-next 4/9] bpf: Add bpf_refcount_acquire kfunc Dave Marchevsky
2023-04-15 20:18 ` [PATCH v2 bpf-next 5/9] bpf: Migrate bpf_rbtree_add and bpf_list_push_{front,back} to possibly fail Dave Marchevsky
2023-04-16 1:11 ` Alexei Starovoitov
2023-04-17 18:08 ` Dave Marchevsky
2023-04-15 20:18 ` [PATCH v2 bpf-next 6/9] selftests/bpf: Modify linked_list tests to work with macro-ified inserts Dave Marchevsky
2023-04-15 20:18 ` [PATCH v2 bpf-next 7/9] bpf: Migrate bpf_rbtree_remove to possibly fail Dave Marchevsky
2023-04-15 20:18 ` [PATCH v2 bpf-next 8/9] bpf: Centralize btf_field-specific initialization logic Dave Marchevsky
2023-04-15 20:18 ` [PATCH v2 bpf-next 9/9] selftests/bpf: Add refcounted_kptr tests Dave Marchevsky
2023-04-21 22:17 ` Kumar Kartikeya Dwivedi
2023-04-21 23:49 ` Alexei Starovoitov
2023-04-22 2:06 ` Kumar Kartikeya Dwivedi
2023-04-22 2:18 ` Alexei Starovoitov
2023-04-25 6:53 ` Dave Marchevsky
2023-04-16 0:50 ` patchwork-bot+netdevbpf [this message]
2023-04-22 2:03 ` [PATCH v2 bpf-next 0/9] Shared ownership for local kptrs Kumar Kartikeya Dwivedi
2023-04-22 3:21 ` Alexei Starovoitov
2023-04-22 18:42 ` Kumar Kartikeya Dwivedi
2023-04-22 21:25 ` Alexei Starovoitov
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=168160621950.14536.17272966925999064717.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=davemarchevsky@fb.com \
--cc=kernel-team@fb.com \
--cc=martin.lau@kernel.org \
/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