From: patchwork-bot+netdevbpf@kernel.org
To: Xuewen Yan <xuewen.yan@unisoc.com>
Cc: song@kernel.org, jolsa@kernel.org, andrii@kernel.org,
daniel@iogearbox.net, rostedt@goodmis.org, ast@kernel.org,
mhiramat@kernel.org, bpf@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
xuewen.yan94@gmail.com, di.shen@unisoc.com
Subject: Re: [PATCH] Revert "bpf: remove unnecessary rcu_read_{lock,unlock}() in multi-uprobe attach logic"
Date: Thu, 22 May 2025 15:00:29 +0000 [thread overview]
Message-ID: <174792602976.2907244.15716912232653968267.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250520054943.5002-1-xuewen.yan@unisoc.com>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Tue, 20 May 2025 13:49:43 +0800 you wrote:
> From: Di Shen <di.shen@unisoc.com>
>
> This reverts commit 4a8f635a60540888dab3804992e86410360339c8.
>
> Althought get_pid_task() internally already calls rcu_read_lock() and
> rcu_read_unlock(), the find_vpid() was not.
>
> [...]
Here is the summary with links:
- Revert "bpf: remove unnecessary rcu_read_{lock,unlock}() in multi-uprobe attach logic"
https://git.kernel.org/bpf/bpf-next/c/4e2e6841ff76
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:[~2025-05-22 14:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-20 5:49 [PATCH] Revert "bpf: remove unnecessary rcu_read_{lock,unlock}() in multi-uprobe attach logic" Xuewen Yan
2025-05-20 20:07 ` Alexei Starovoitov
2025-05-20 20:30 ` Andrii Nakryiko
2025-05-22 15: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=174792602976.2907244.15716912232653968267.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=di.shen@unisoc.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=rostedt@goodmis.org \
--cc=song@kernel.org \
--cc=xuewen.yan94@gmail.com \
--cc=xuewen.yan@unisoc.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