BPF List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Leon Hwang <leon.hwang@linux.dev>
Cc: bpf@vger.kernel.org, ast@kernel.org, andrii@kernel.org,
	daniel@iogearbox.net, yepeilin@google.com, martin.lau@linux.dev,
	eddyz87@gmail.com, song@kernel.org, yonghong.song@linux.dev,
	kernel-patches-bot@fb.com
Subject: Re: [PATCH bpf v3 0/2] bpf: Reject bpf_timer for PREEMPT_RT
Date: Wed, 10 Sep 2025 19:40:08 +0000	[thread overview]
Message-ID: <175753320852.1544970.3158513977352960891.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250910125740.52172-1-leon.hwang@linux.dev>

Hello:

This series was applied to bpf/bpf.git (master)
by Alexei Starovoitov <ast@kernel.org>:

On Wed, 10 Sep 2025 20:57:38 +0800 you wrote:
> While running './test_progs -t timer' to validate the test case from
> "selftests/bpf: Introduce experimental bpf_in_interrupt()"[0] for
> PREEMPT_RT, I encountered a kernel warning:
> 
> BUG: sleeping function called from invalid context at kernel/locking/spinlock_rt.c:48
> 
> To address this, reject bpf_timer usage in the verifier when
> PREEMPT_RT is enabled, and skip the corresponding timer selftests.
> 
> [...]

Here is the summary with links:
  - [bpf,v3,1/2] bpf: Reject bpf_timer for PREEMPT_RT
    https://git.kernel.org/bpf/bpf/c/e25ddfb388c8
  - [bpf,v3,2/2] selftests/bpf: Skip timer cases when bpf_timer is not supported
    https://git.kernel.org/bpf/bpf/c/fbdd61c94bcb

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2025-09-10 19:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-10 12:57 [PATCH bpf v3 0/2] bpf: Reject bpf_timer for PREEMPT_RT Leon Hwang
2025-09-10 12:57 ` [PATCH bpf v3 1/2] " Leon Hwang
2025-09-10 12:57 ` [PATCH bpf v3 2/2] selftests/bpf: Skip timer cases when bpf_timer is not supported Leon Hwang
2025-09-10 19:40 ` 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=175753320852.1544970.3158513977352960891.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-patches-bot@fb.com \
    --cc=leon.hwang@linux.dev \
    --cc=martin.lau@linux.dev \
    --cc=song@kernel.org \
    --cc=yepeilin@google.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