From: patchwork-bot+netdevbpf@kernel.org
To: Kumar Kartikeya Dwivedi <memxor@gmail.com>
Cc: bpf@vger.kernel.org, kkd@meta.com, ast@kernel.org,
andrii@kernel.org, daniel@iogearbox.net, martin.lau@kernel.org,
eddyz87@gmail.com, kernel-team@fb.com
Subject: Re: [PATCH bpf-next v1 0/3] Fix resource leak checks for tail calls
Date: Mon, 04 Nov 2024 01:00:34 +0000 [thread overview]
Message-ID: <173068203449.3594539.9649006550556738522.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241103225940.1408302-1-memxor@gmail.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Sun, 3 Nov 2024 14:59:37 -0800 you wrote:
> This set contains a fix for detecting unreleased RCU read locks or
> unfinished preempt_disable sections when performing a tail call. Spin
> locks are prevented by accident since they don't allow any function
> calls, including tail calls (modelled as call instruction to a helper),
> so we ensure they are checked as well, in preparation for relaxing
> function call restricton for critical sections in the future.
>
> [...]
Here is the summary with links:
- [bpf-next,v1,1/3] bpf: Tighten tail call checks for lingering locks, RCU, preempt_disable
https://git.kernel.org/bpf/bpf-next/c/46f7ed32f7a8
- [bpf-next,v1,2/3] bpf: Unify resource leak checks
https://git.kernel.org/bpf/bpf-next/c/d402755ced2e
- [bpf-next,v1,3/3] selftests/bpf: Add tests for tail calls with locks and refs
https://git.kernel.org/bpf/bpf-next/c/711df091dea9
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-11-04 1:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-03 22:59 [PATCH bpf-next v1 0/3] Fix resource leak checks for tail calls Kumar Kartikeya Dwivedi
2024-11-03 22:59 ` [PATCH bpf-next v1 1/3] bpf: Tighten tail call checks for lingering locks, RCU, preempt_disable Kumar Kartikeya Dwivedi
2024-11-03 22:59 ` [PATCH bpf-next v1 2/3] bpf: Unify resource leak checks Kumar Kartikeya Dwivedi
2024-11-03 22:59 ` [PATCH bpf-next v1 3/3] selftests/bpf: Add tests for tail calls with locks and refs Kumar Kartikeya Dwivedi
2024-11-04 1: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=173068203449.3594539.9649006550556738522.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=kernel-team@fb.com \
--cc=kkd@meta.com \
--cc=martin.lau@kernel.org \
--cc=memxor@gmail.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