From: patchwork-bot+netdevbpf@kernel.org
To: Kumar Kartikeya Dwivedi <memxor@gmail.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, yhs@fb.com,
andrii@kernel.org, daniel@iogearbox.net
Subject: Re: [PATCH bpf v2 0/3] Fix reference state management for synchronous callbacks
Date: Tue, 23 Aug 2022 23:30:16 +0000 [thread overview]
Message-ID: <166129741676.15279.2242567262096963454.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220823012759.24844-1-memxor@gmail.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Tue, 23 Aug 2022 03:27:56 +0200 you wrote:
> This is patch 1, 2 + their individual tests split into a separate series from
> the RFC, so that these can be taken in, while we continue working towards a fix
> for handling stack access inside the callback.
>
> Changelog:
> ----------
> v1 -> v2:
> v1: https://lore.kernel.org/bpf/20220822131923.21476-1-memxor@gmail.com
>
> [...]
Here is the summary with links:
- [bpf,v2,1/3] bpf: Move bpf_loop and bpf_for_each_map_elem under CAP_BPF
https://git.kernel.org/bpf/bpf-next/c/5679ff2f138f
- [bpf,v2,2/3] bpf: Fix reference state management for synchronous callbacks
https://git.kernel.org/bpf/bpf-next/c/2e5e0e8ede02
- [bpf,v2,3/3] selftests/bpf: Add tests for reference state fixes for callbacks
https://git.kernel.org/bpf/bpf-next/c/3cf7e7d8685c
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-08-23 23:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-23 1:27 [PATCH bpf v2 0/3] Fix reference state management for synchronous callbacks Kumar Kartikeya Dwivedi
2022-08-23 1:31 ` [PATCH bpf v2 1/3] bpf: Move bpf_loop and bpf_for_each_map_elem under CAP_BPF Kumar Kartikeya Dwivedi
2022-08-23 1:31 ` [PATCH bpf v2 2/3] bpf: Fix reference state management for synchronous callbacks Kumar Kartikeya Dwivedi
2022-08-23 1:32 ` [PATCH bpf v2 3/3] selftests/bpf: Add tests for reference state fixes for callbacks Kumar Kartikeya Dwivedi
2022-08-23 23:30 ` 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=166129741676.15279.2242567262096963454.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=memxor@gmail.com \
--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