From: patchwork-bot+netdevbpf@kernel.org
To: Varun R Mallya <varunrmallya@gmail.com>
Cc: bpf@vger.kernel.org, leon.hwang@linux.dev, memxor@gmail.com,
jolsa@kernel.org, ast@kernel.org, daniel@iogearbox.net,
yonghong.song@linux.dev, rostedt@goodmis.org,
linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org
Subject: Re: [PATCH bpf-next v5 0/2] Reject sleepable kprobe_multi programs at attach time
Date: Thu, 09 Apr 2026 01:20:08 +0000 [thread overview]
Message-ID: <177569760855.941108.1194858936384188273.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260408190137.101418-1-varunrmallya@gmail.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Thu, 9 Apr 2026 00:31:35 +0530 you wrote:
> These patches fix an issue where sleepable kprobe_multi programs
> were allowed to attach, leading to "sleeping function called from invalid
> context" splats.
>
> Because kprobe.multi programs run in atomic/RCU context, they cannot
> sleep. However, `bpf_kprobe_multi_link_attach()` previously lacked
> validation for the `prog->sleepable` flag. This allowed sleepable
> helpers, such as `bpf_copy_from_user()`, to be invoked from an invalid
> non-sleepable context.
>
> [...]
Here is the summary with links:
- [bpf-next,v5,1/2] bpf: Reject sleepable kprobe_multi programs at attach time
(no matching commit)
- [bpf-next,v5,2/2] selftests/bpf: Add test to ensure kprobe_multi is not sleepable
https://git.kernel.org/bpf/bpf-next/c/c7cab53f9d52
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:[~2026-04-09 1:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-08 19:01 [PATCH bpf-next v5 0/2] Reject sleepable kprobe_multi programs at attach time Varun R Mallya
2026-04-08 19:01 ` [PATCH bpf-next v5 1/2] bpf: " Varun R Mallya
2026-04-08 19:01 ` [PATCH bpf-next v5 2/2] selftests/bpf: Add test to ensure kprobe_multi is not sleepable Varun R Mallya
2026-04-09 1:20 ` 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=177569760855.941108.1194858936384188273.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=jolsa@kernel.org \
--cc=leon.hwang@linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=memxor@gmail.com \
--cc=rostedt@goodmis.org \
--cc=varunrmallya@gmail.com \
--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