From: patchwork-bot+netdevbpf@kernel.org
To: Amery Hung <amery.hung@bytedance.com>
Cc: bpf@vger.kernel.org, daniel@iogearbox.net, andrii@kernel.org,
alexei.starovoitov@gmail.com, martin.lau@kernel.org,
houtao@huaweicloud.com, sinquersw@gmail.com,
davemarchevsky@fb.com, ameryhung@gmail.com
Subject: Re: [PATCH v4 bpf-next 0/5] Support bpf_kptr_xchg into local kptr
Date: Fri, 23 Aug 2024 18:50:33 +0000 [thread overview]
Message-ID: <172443903354.3055350.8541667784916946733.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240813212424.2871455-1-amery.hung@bytedance.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Tue, 13 Aug 2024 21:24:19 +0000 you wrote:
> This revision adds substaintial changes to patch 2 to support structures
> with kptr as the only special btf type. The test is split into
> local_kptr_stash and task_kfunc_success to remove dependencies on
> bpf_testmod that would break veristat results.
>
> This series allows stashing kptr into local kptr. Currently, kptrs are
> only allowed to be stashed into map value with bpf_kptr_xchg(). A
> motivating use case of this series is to enable adding referenced kptr to
> bpf_rbtree or bpf_list by using allocated object as graph node and the
> storage of referenced kptr. For example, a bpf qdisc [0] enqueuing a
> referenced kptr to a struct sk_buff* to a bpf_list serving as a fifo:
>
> [...]
Here is the summary with links:
- [v4,bpf-next,1/5] bpf: Let callers of btf_parse_kptr() track life cycle of prog btf
https://git.kernel.org/bpf/bpf-next/c/c5ef53420f46
- [v4,bpf-next,2/5] bpf: Search for kptrs in prog BTF structs
https://git.kernel.org/bpf/bpf-next/c/7a851ecb1806
- [v4,bpf-next,3/5] bpf: Rename ARG_PTR_TO_KPTR -> ARG_KPTR_XCHG_DEST
https://git.kernel.org/bpf/bpf-next/c/d59232afb034
- [v4,bpf-next,4/5] bpf: Support bpf_kptr_xchg into local kptr
https://git.kernel.org/bpf/bpf-next/c/b0966c724584
- [v4,bpf-next,5/5] selftests/bpf: Test bpf_kptr_xchg stashing into local kptr
https://git.kernel.org/bpf/bpf-next/c/91c96842ab1e
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-08-23 18:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-13 21:24 [PATCH v4 bpf-next 0/5] Support bpf_kptr_xchg into local kptr Amery Hung
2024-08-13 21:24 ` [PATCH v4 bpf-next 1/5] bpf: Let callers of btf_parse_kptr() track life cycle of prog btf Amery Hung
2024-08-13 21:24 ` [PATCH v4 bpf-next 2/5] bpf: Search for kptrs in prog BTF structs Amery Hung
2024-08-13 21:24 ` [PATCH v4 bpf-next 3/5] bpf: Rename ARG_PTR_TO_KPTR -> ARG_KPTR_XCHG_DEST Amery Hung
2024-08-13 21:24 ` [PATCH v4 bpf-next 4/5] bpf: Support bpf_kptr_xchg into local kptr Amery Hung
2024-08-13 21:24 ` [PATCH v4 bpf-next 5/5] selftests/bpf: Test bpf_kptr_xchg stashing " Amery Hung
2024-08-23 18:48 ` Alexei Starovoitov
2024-08-23 23:59 ` Amery Hung
2024-08-23 18: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=172443903354.3055350.8541667784916946733.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alexei.starovoitov@gmail.com \
--cc=amery.hung@bytedance.com \
--cc=ameryhung@gmail.com \
--cc=andrii@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davemarchevsky@fb.com \
--cc=houtao@huaweicloud.com \
--cc=martin.lau@kernel.org \
--cc=sinquersw@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