From: patchwork-bot+netdevbpf@kernel.org
To: David Vernet <void@manifault.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
andrii@kernel.org, martin.lau@linux.dev, song@kernel.org,
yhs@fb.com, john.fastabend@gmail.com, kpsingh@kernel.org,
sdf@google.com, haoluo@google.com, jolsa@kernel.org,
linux-kernel@vger.kernel.org, kernel-team@meta.com
Subject: Re: [PATCH bpf-next v2 0/3] Enable RCU semantics for task kptrs
Date: Sat, 01 Apr 2023 16:20:17 +0000 [thread overview]
Message-ID: <168036601729.14852.14484701453991641814.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230331195733.699708-1-void@manifault.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Fri, 31 Mar 2023 14:57:30 -0500 you wrote:
> In commit 22df776a9a86 ("tasks: Extract rcu_users out of union"), the
> 'refcount_t rcu_users' field was extracted out of a union with the
> 'struct rcu_head rcu' field. This allows us to use the field for
> refcounting struct task_struct with RCU protection, as the RCU callback
> no longer flips rcu_users to be nonzero after the callback is scheduled.
>
> This patch set leverages this to do a few things:
>
> [...]
Here is the summary with links:
- [bpf-next,v2,1/3] bpf: Make struct task_struct an RCU-safe type
https://git.kernel.org/bpf/bpf-next/c/d02c48fa1139
- [bpf-next,v2,2/3] bpf: Remove now-defunct task kfuncs
https://git.kernel.org/bpf/bpf-next/c/f85671c6ef46
- [bpf-next,v2,3/3] bpf,docs: Update documentation to reflect new task kfuncs
https://git.kernel.org/bpf/bpf-next/c/db9d479ab59b
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:[~2023-04-01 16:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-31 19:57 [PATCH bpf-next v2 0/3] Enable RCU semantics for task kptrs David Vernet
2023-03-31 19:57 ` [PATCH bpf-next v2 1/3] bpf: Make struct task_struct an RCU-safe type David Vernet
2023-03-31 19:57 ` [PATCH bpf-next v2 2/3] bpf: Remove now-defunct task kfuncs David Vernet
2023-03-31 19:57 ` [PATCH bpf-next v2 3/3] bpf,docs: Update documentation to reflect new " David Vernet
2023-04-01 16:20 ` 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=168036601729.14852.14484701453991641814.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=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kernel-team@meta.com \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=sdf@google.com \
--cc=song@kernel.org \
--cc=void@manifault.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.