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@meta.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,
matus.jokay@stuba.sk
Subject: Re: [PATCH bpf-next] bpf: Don't use rcu_users to refcount in task kfuncs
Date: Wed, 07 Dec 2022 00:50:15 +0000 [thread overview]
Message-ID: <167037421590.21168.15544394333663900920.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221206210538.597606-1-void@manifault.com>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Tue, 6 Dec 2022 15:05:38 -0600 you wrote:
> A series of prior patches added some kfuncs that allow struct
> task_struct * objects to be used as kptrs. These kfuncs leveraged the
> 'refcount_t rcu_users' field of the task for performing refcounting.
> This field was used instead of 'refcount_t usage', as we wanted to
> leverage the safety provided by RCU for ensuring a task's lifetime.
>
> A struct task_struct is refcounted by two different refcount_t fields:
>
> [...]
Here is the summary with links:
- [bpf-next] bpf: Don't use rcu_users to refcount in task kfuncs
https://git.kernel.org/bpf/bpf-next/c/156ed20d22ee
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-12-07 0:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-06 21:05 [PATCH bpf-next] bpf: Don't use rcu_users to refcount in task kfuncs David Vernet
2022-12-07 0: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=167037421590.21168.15544394333663900920.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=matus.jokay@stuba.sk \
--cc=sdf@google.com \
--cc=song@kernel.org \
--cc=void@manifault.com \
--cc=yhs@meta.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