From: patchwork-bot+netdevbpf@kernel.org
To: Kui-Feng Lee <thinker.li@gmail.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, martin.lau@linux.dev,
kernel-team@meta.com, andrii@kernel.org, sinquersw@gmail.com,
kuifeng@meta.com
Subject: Re: [PATCH bpf-next v7 0/8] Notify user space when a struct_ops object is detached/unregistered
Date: Thu, 30 May 2024 22:40:33 +0000 [thread overview]
Message-ID: <171710883332.22324.8286442445839775054.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240530065946.979330-1-thinker.li@gmail.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Martin KaFai Lau <martin.lau@kernel.org>:
On Wed, 29 May 2024 23:59:38 -0700 you wrote:
> From: Kui-Feng Lee <kuifeng@meta.com>
>
> The subsystems managing struct_ops objects may need to detach a
> struct_ops object due to errors or other reasons. It would be useful
> to notify user space programs so that error recovery or logging can be
> carried out.
>
> [...]
Here is the summary with links:
- [bpf-next,v7,1/8] bpf: pass bpf_struct_ops_link to callbacks in bpf_struct_ops.
https://git.kernel.org/bpf/bpf-next/c/73287fe22872
- [bpf-next,v7,2/8] bpf: enable detaching links of struct_ops objects.
https://git.kernel.org/bpf/bpf-next/c/6fb2544ea149
- [bpf-next,v7,3/8] bpf: support epoll from bpf struct_ops links.
https://git.kernel.org/bpf/bpf-next/c/1adddc97aa44
- [bpf-next,v7,4/8] bpf: export bpf_link_inc_not_zero.
https://git.kernel.org/bpf/bpf-next/c/67c3e8353f45
- [bpf-next,v7,5/8] selftests/bpf: test struct_ops with epoll
https://git.kernel.org/bpf/bpf-next/c/1a4b858b6a04
- [bpf-next,v7,6/8] selftests/bpf: detach a struct_ops link from the subsystem managing it.
(no matching commit)
- [bpf-next,v7,7/8] selftests/bpf: make sure bpf_testmod handling racing link destroying well.
(no matching commit)
- [bpf-next,v7,8/8] bpftool: Change pid_iter.bpf.c to comply with the change of bpf_link_fops.
https://git.kernel.org/bpf/bpf-next/c/d14c1fac0c97
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-05-30 22:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-30 6:59 [PATCH bpf-next v7 0/8] Notify user space when a struct_ops object is detached/unregistered thinker.li
2024-05-30 6:59 ` [PATCH bpf-next v7 1/8] bpf: pass bpf_struct_ops_link to callbacks in bpf_struct_ops thinker.li
2024-05-30 6:59 ` [PATCH bpf-next v7 2/8] bpf: enable detaching links of struct_ops objects thinker.li
2024-05-30 6:59 ` [PATCH bpf-next v7 3/8] bpf: support epoll from bpf struct_ops links thinker.li
2024-05-30 6:59 ` [PATCH bpf-next v7 4/8] bpf: export bpf_link_inc_not_zero thinker.li
2024-05-30 6:59 ` [PATCH bpf-next v7 5/8] selftests/bpf: test struct_ops with epoll thinker.li
2024-05-30 6:59 ` [PATCH bpf-next v7 6/8] selftests/bpf: detach a struct_ops link from the subsystem managing it thinker.li
2024-05-30 23:02 ` Martin KaFai Lau
2024-05-30 6:59 ` [PATCH bpf-next v7 7/8] selftests/bpf: make sure bpf_testmod handling racing link destroying well thinker.li
2024-05-30 6:59 ` [PATCH bpf-next v7 8/8] bpftool: Change pid_iter.bpf.c to comply with the change of bpf_link_fops thinker.li
2024-05-30 22:40 ` 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=171710883332.22324.8286442445839775054.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=kernel-team@meta.com \
--cc=kuifeng@meta.com \
--cc=martin.lau@linux.dev \
--cc=sinquersw@gmail.com \
--cc=thinker.li@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