From: patchwork-bot+netdevbpf@kernel.org
To: Juntong Deng <juntong.deng@outlook.com>
Cc: ast@kernel.org, daniel@iogearbox.net, john.fastabend@gmail.com,
andrii@kernel.org, martin.lau@linux.dev, eddyz87@gmail.com,
song@kernel.org, yonghong.song@linux.dev, kpsingh@kernel.org,
sdf@fomichev.me, haoluo@google.com, jolsa@kernel.org,
memxor@gmail.com, snorcht@gmail.com, bpf@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH bpf-next 1/2] bpf: Add bpf_task_from_vpid() kfunc
Date: Tue, 15 Oct 2024 02:00:31 +0000 [thread overview]
Message-ID: <172895763151.696768.12853090794855329864.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <AM6PR03MB5848E50DA58F79CDE65433C399442@AM6PR03MB5848.eurprd03.prod.outlook.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Mon, 14 Oct 2024 10:21:08 +0100 you wrote:
> bpf_task_from_pid() that currently exists looks up the
> struct task_struct corresponding to the pid in the root pid
> namespace (init_pid_ns).
>
> This patch adds bpf_task_from_vpid() which looks up the
> struct task_struct corresponding to vpid in the pid namespace
> of the current process.
>
> [...]
Here is the summary with links:
- [bpf-next,1/2] bpf: Add bpf_task_from_vpid() kfunc
https://git.kernel.org/bpf/bpf-next/c/6dce087f24e5
- [bpf-next,2/2] selftests/bpf: Add tests for bpf_task_from_vpid() kfunc
https://git.kernel.org/bpf/bpf-next/c/108e7b4db83b
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-10-15 2:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-14 9:21 [PATCH bpf-next 1/2] bpf: Add bpf_task_from_vpid() kfunc Juntong Deng
2024-10-14 9:25 ` [PATCH bpf-next 2/2] selftests/bpf: Add tests for " Juntong Deng
2024-10-15 2:00 ` 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=172895763151.696768.12853090794855329864.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=eddyz87@gmail.com \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=juntong.deng@outlook.com \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=memxor@gmail.com \
--cc=sdf@fomichev.me \
--cc=snorcht@gmail.com \
--cc=song@kernel.org \
--cc=yonghong.song@linux.dev \
/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