From: patchwork-bot+netdevbpf@kernel.org
To: Hou Tao <houtao@huaweicloud.com>
Cc: bpf@vger.kernel.org, martin.lau@linux.dev,
alexei.starovoitov@gmail.com, andrii@kernel.org,
eddyz87@gmail.com, song@kernel.org, haoluo@google.com,
yonghong.song@linux.dev, daniel@iogearbox.net,
kpsingh@kernel.org, sdf@fomichev.me, jolsa@kernel.org,
john.fastabend@gmail.com, houtao1@huawei.com
Subject: Re: [PATCH bpf-next] bpf: Check rcu_read_lock_trace_held() in bpf_map_lookup_percpu_elem()
Date: Tue, 27 May 2025 17:50:32 +0000 [thread overview]
Message-ID: <174836823200.1725298.10199388427709310337.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250526062534.1105938-1-houtao@huaweicloud.com>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Mon, 26 May 2025 14:25:34 +0800 you wrote:
> From: Hou Tao <houtao1@huawei.com>
>
> bpf_map_lookup_percpu_elem() helper is also available for sleepable bpf
> program. When BPF JIT is disabled or under 32-bit host,
> bpf_map_lookup_percpu_elem() will not be inlined. Using it in a
> sleepable bpf program will trigger the warning in
> bpf_map_lookup_percpu_elem(), because the bpf program only holds
> rcu_read_lock_trace lock. Therefore, add the missed check.
>
> [...]
Here is the summary with links:
- [bpf-next] bpf: Check rcu_read_lock_trace_held() in bpf_map_lookup_percpu_elem()
https://git.kernel.org/bpf/bpf-next/c/d4965578267e
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-27 17:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-26 6:25 [PATCH bpf-next] bpf: Check rcu_read_lock_trace_held() in bpf_map_lookup_percpu_elem() Hou Tao
2025-05-27 17: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=174836823200.1725298.10199388427709310337.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alexei.starovoitov@gmail.com \
--cc=andrii@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=haoluo@google.com \
--cc=houtao1@huawei.com \
--cc=houtao@huaweicloud.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=martin.lau@linux.dev \
--cc=sdf@fomichev.me \
--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