From: patchwork-bot+netdevbpf@kernel.org
To: Emil Tsalapatis <emil@etsalapatis.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
andrii@kernel.org, eddyz87@gmail.com
Subject: Re: [PATCH v2 0/2] bpf: Allow bpf_for/bpf_repeat while holding spin
Date: Mon, 06 Jan 2025 19:10:29 +0000 [thread overview]
Message-ID: <173619062952.3592870.1339065672417521709.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250104202528.882482-1-emil@etsalapatis.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Sat, 4 Jan 2025 15:25:26 -0500 you wrote:
> From: Emil Tsalapatis (Meta) <emil@etsalapatis.com>
>
> In BPF programs, kfunc calls while holding a lock are not allowed
> because kfuncs may sleep by default. The exception to this rule are the
> functions in special_kfunc_list, which are guaranteed to not sleep. The
> bpf_iter_num_* functions used by the bpf_for and bpf_repeat macros make
> no function calls themselves, and as such are guaranteed to not sleep.
> Add them to special_kfunc_list to allow them within BPF spinlock
> critical sections.
>
> [...]
Here is the summary with links:
- [v2,1/2] bpf: Allow bpf_for/bpf_repeat calls while holding a spinlock
https://git.kernel.org/bpf/bpf-next/c/512816403ece
- [v2,2/2] selftests/bpf: test bpf_for within spin lock section
https://git.kernel.org/bpf/bpf-next/c/87091dd986db
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-01-06 19:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-04 20:25 [PATCH v2 0/2] bpf: Allow bpf_for/bpf_repeat while holding spin Emil Tsalapatis
2025-01-04 20:25 ` [PATCH v2 1/2] bpf: Allow bpf_for/bpf_repeat calls while holding a spinlock Emil Tsalapatis
2025-01-04 20:25 ` [PATCH v2 2/2] selftests/bpf: test bpf_for within spin lock section Emil Tsalapatis
2025-01-06 19: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=173619062952.3592870.1339065672417521709.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=emil@etsalapatis.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