From: patchwork-bot+netdevbpf@kernel.org
To: Alexei Starovoitov <alexei.starovoitov@gmail.com>
Cc: bpf@vger.kernel.org, daniel@iogearbox.net, andrii@kernel.org,
eddyz87@gmail.com, memxor@gmail.com
Subject: Re: [PATCH bpf v2 0/9] bpf: One may_goto time slice per prog invocation
Date: Mon, 02 Nov 2026 22:30:07 +0000 [thread overview]
Message-ID: <179365860780.698908.5907895296789824296.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261031215543.682284-1-alexei.starovoitov@gmail.com>
Hello:
This series was applied to bpf/bpf.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Sat, 31 Oct 2026 21:55:34 +0000 you wrote:
> From: Alexei Starovoitov <ast@kernel.org>
>
> may_goto stops a loop that the verifier cannot bound: after 250 ms the loop
> must exit. The count and the timestamp are in the stack frame of the
> function that contains the loop. So the limit is for one call of a subprog,
> not for one invocation of a prog. Loops that nest across calls multiply it,
> and 9 insns lock up a cpu:
>
> [...]
Here is the summary with links:
- [bpf,v2,1/9] bpf: Emit timed may_goto for JITed progs only
https://git.kernel.org/bpf/bpf/c/1ddffb57b362
- [bpf,v2,2/9] selftests/bpf: Don't cast a pointer to .bss in arena_htab_asm
https://git.kernel.org/bpf/bpf/c/fcda8096dc5d
- [bpf,v2,3/9] selftests/bpf: Give the first loop of cond_break5 an end
https://git.kernel.org/bpf/bpf/c/40a3a2e686f8
- [bpf,v2,4/9] selftests/bpf: End the loop of parallel_test_bitmap after 50 ms
https://git.kernel.org/bpf/bpf/c/5eced83779fd
- [bpf,v2,5/9] s390/bpf: Support internal-only MOV instruction to resolve per-CPU addrs
https://git.kernel.org/bpf/bpf/c/85b6a11252ba
- [bpf,v2,6/9] bpf: Pass a pointer to arch_bpf_timed_may_goto()
https://git.kernel.org/bpf/bpf/c/78821f4d8d18
- [bpf,v2,7/9] bpf: One may_goto time slice per prog invocation
https://git.kernel.org/bpf/bpf/c/ec274bb4665c
- [bpf,v2,8/9] bpf: End bpf_loop() when the time of may_goto is up
https://git.kernel.org/bpf/bpf/c/c16c6c4683cc
- [bpf,v2,9/9] selftests/bpf: Test one may_goto time slice per prog invocation
https://git.kernel.org/bpf/bpf/c/9d8affd7b6f5
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-11-02 22:30 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-31 21:55 [PATCH bpf v2 0/9] bpf: One may_goto time slice per prog invocation Alexei Starovoitov
2026-10-31 21:55 ` [PATCH bpf v2 1/9] bpf: Emit timed may_goto for JITed progs only Alexei Starovoitov
2026-10-31 21:55 ` [PATCH bpf v2 2/9] selftests/bpf: Don't cast a pointer to .bss in arena_htab_asm Alexei Starovoitov
2026-10-31 21:55 ` [PATCH bpf v2 3/9] selftests/bpf: Give the first loop of cond_break5 an end Alexei Starovoitov
2026-10-31 21:55 ` [PATCH bpf v2 4/9] selftests/bpf: End the loop of parallel_test_bitmap after 50 ms Alexei Starovoitov
2026-10-31 21:55 ` [PATCH bpf v2 5/9] s390/bpf: Support internal-only MOV instruction to resolve per-CPU addrs Alexei Starovoitov
2026-10-31 22:26 ` bot+bpf-ci
2026-10-31 21:55 ` [PATCH bpf v2 6/9] bpf: Pass a pointer to arch_bpf_timed_may_goto() Alexei Starovoitov
2026-10-31 21:55 ` [PATCH bpf v2 7/9] bpf: One may_goto time slice per prog invocation Alexei Starovoitov
2026-10-31 22:25 ` sashiko-bot
2026-10-31 22:30 ` Alexei Starovoitov
2026-10-31 22:37 ` bot+bpf-ci
2026-10-31 22:50 ` Alexei Starovoitov
2026-10-31 21:55 ` [PATCH bpf v2 8/9] bpf: End bpf_loop() when the time of may_goto is up Alexei Starovoitov
2026-10-31 21:55 ` [PATCH bpf v2 9/9] selftests/bpf: Test one may_goto time slice per prog invocation Alexei Starovoitov
2026-10-31 22:12 ` sashiko-bot
2026-10-31 22:31 ` Alexei Starovoitov
2026-11-02 22:30 ` 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=179365860780.698908.5907895296789824296.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=eddyz87@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.