From: patchwork-bot+netdevbpf@kernel.org
To: David Vernet <void@manifault.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, andrii@kernel.org,
daniel@iogearbox.net, martin.lau@linux.dev, yhs@fb.com,
song@kernel.org, sdf@google.com, john.fastabend@gmail.com,
kpsingh@kernel.org, jolsa@kernel.org, haoluo@google.com,
tj@kernel.org, kernel-team@fb.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH bpf-next 0/2] Add kfunc for doing pid -> task lookup
Date: Thu, 24 Nov 2022 02:10:15 +0000 [thread overview]
Message-ID: <166925581574.23700.5716179637470412822.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221122145300.251210-1-void@manifault.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Tue, 22 Nov 2022 08:52:58 -0600 you wrote:
> A series of prior patches added support for storing struct task_struct *
> objects as kptrs. This patch set proposes extending this with another
> kfunc called bpf_task_from_pid() which performs a lookup of a task from
> its pid, from the root pid namespace idr.
>
> This allows BPF programs that don't have a kptr to a task, to instead
> perform a lookup by pid. This will be useful for programs that are
> tracking pids and want, e.g., to do a lookup to find task->comm.
>
> [...]
Here is the summary with links:
- [bpf-next,1/2] bpf: Add bpf_task_from_pid() kfunc
https://git.kernel.org/bpf/bpf-next/c/3f0e6f2b41d3
- [bpf-next,2/2] selftests/bpf: Add selftests for bpf_task_from_pid()
https://git.kernel.org/bpf/bpf-next/c/f471748b7fe5
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-11-24 2:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-22 14:52 [PATCH bpf-next 0/2] Add kfunc for doing pid -> task lookup David Vernet
2022-11-22 14:52 ` [PATCH bpf-next 1/2] bpf: Add bpf_task_from_pid() kfunc David Vernet
2022-11-22 14:53 ` [PATCH bpf-next 2/2] selftests/bpf: Add selftests for bpf_task_from_pid() David Vernet
2022-11-24 2:10 ` 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=166925581574.23700.5716179637470412822.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@fb.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=tj@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox