BPF List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Alexei Starovoitov <alexei.starovoitov@gmail.com>
Cc: bpf@vger.kernel.org, daniel@iogearbox.net, andrii@kernel.org,
	martin.lau@kernel.org, memxor@gmail.com,
	mykyta.yatsenko5@gmail.com, kernel-team@fb.com
Subject: Re: [PATCH v9 bpf-next 0/9] bpf: Avoid locks in bpf_timer and bpf_wq
Date: Wed, 04 Feb 2026 01:10:18 +0000	[thread overview]
Message-ID: <177016741813.2125760.7860406569007550057.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260201025403.66625-1-alexei.starovoitov@gmail.com>

Hello:

This series was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:

On Sat, 31 Jan 2026 18:53:54 -0800 you wrote:
> From: Alexei Starovoitov <ast@kernel.org>
> 
> This series reworks implementation of BPF timer and workqueue APIs to
> make them usable from any context.
> 
> Signed-off-by: Alexei Starovoitov <ast@kernel.org>
> Signed-off-by: Mykyta Yatsenko <yatsenko@meta.com>
> 
> [...]

Here is the summary with links:
  - [v9,bpf-next,1/9] bpf: Enable bpf_timer and bpf_wq in any context
    https://git.kernel.org/bpf/bpf-next/c/1bfbc267ec91
  - [v9,bpf-next,2/9] bpf: Add verifier support for bpf_timer argument in kfuncs
    https://git.kernel.org/bpf/bpf-next/c/19bd300e22c2
  - [v9,bpf-next,3/9] bpf: Introduce bpf_timer_cancel_async() kfunc
    https://git.kernel.org/bpf/bpf-next/c/a7e172aa4ca2
  - [v9,bpf-next,4/9] selftests/bpf: Refactor timer selftests
    https://git.kernel.org/bpf/bpf-next/c/10653c0dd868
  - [v9,bpf-next,5/9] selftests/bpf: Add stress test for timer async cancel
    https://git.kernel.org/bpf/bpf-next/c/d02fdd7195ca
  - [v9,bpf-next,6/9] selftests/bpf: Verify bpf_timer_cancel_async works
    https://git.kernel.org/bpf/bpf-next/c/fe9d205cec8c
  - [v9,bpf-next,7/9] selftests/bpf: Add timer stress test in NMI context
    https://git.kernel.org/bpf/bpf-next/c/083c5a4babad
  - [v9,bpf-next,8/9] selftests/bpf: Removed obsolete tests
    https://git.kernel.org/bpf/bpf-next/c/3f7a8415209e
  - [v9,bpf-next,9/9] selftests/bpf: Add a test to stress bpf_timer_start and map_delete race
    https://git.kernel.org/bpf/bpf-next/c/b135beb07758

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



      parent reply	other threads:[~2026-02-04  1:10 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-01  2:53 [PATCH v9 bpf-next 0/9] bpf: Avoid locks in bpf_timer and bpf_wq Alexei Starovoitov
2026-02-01  2:53 ` [PATCH v9 bpf-next 1/9] bpf: Enable bpf_timer and bpf_wq in any context Alexei Starovoitov
2026-02-02 13:36   ` Mykyta Yatsenko
2026-02-02 17:29     ` Alexei Starovoitov
2026-02-03 22:14   ` Kumar Kartikeya Dwivedi
2026-02-03 23:53   ` Andrii Nakryiko
2026-02-04  0:32     ` Alexei Starovoitov
2026-02-04  0:53       ` Andrii Nakryiko
2026-02-04  0:56         ` Andrii Nakryiko
2026-02-01  2:53 ` [PATCH v9 bpf-next 2/9] bpf: Add verifier support for bpf_timer argument in kfuncs Alexei Starovoitov
2026-02-01  3:15   ` bot+bpf-ci
2026-02-01  2:53 ` [PATCH v9 bpf-next 3/9] bpf: Introduce bpf_timer_cancel_async() kfunc Alexei Starovoitov
2026-02-01  2:53 ` [PATCH v9 bpf-next 4/9] selftests/bpf: Refactor timer selftests Alexei Starovoitov
2026-02-01  2:53 ` [PATCH v9 bpf-next 5/9] selftests/bpf: Add stress test for timer async cancel Alexei Starovoitov
2026-02-01  2:54 ` [PATCH v9 bpf-next 6/9] selftests/bpf: Verify bpf_timer_cancel_async works Alexei Starovoitov
2026-02-01  2:54 ` [PATCH v9 bpf-next 7/9] selftests/bpf: Add timer stress test in NMI context Alexei Starovoitov
2026-02-01  2:54 ` [PATCH v9 bpf-next 8/9] selftests/bpf: Removed obsolete tests Alexei Starovoitov
2026-02-01  2:54 ` [PATCH v9 bpf-next 9/9] selftests/bpf: Add a test to stress bpf_timer_start and map_delete race Alexei Starovoitov
2026-02-01  3:15   ` bot+bpf-ci
2026-02-01  3:30     ` Alexei Starovoitov
2026-02-04  1: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=177016741813.2125760.7860406569007550057.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=kernel-team@fb.com \
    --cc=martin.lau@kernel.org \
    --cc=memxor@gmail.com \
    --cc=mykyta.yatsenko5@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