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, a.s.protopopov@gmail.com
Subject: Re: [PATCH v3 bpf-next 00/11] bpf: fmod_ret for each function that returns errors
Date: Sat, 14 Nov 2026 18:30:07 +0000 [thread overview]
Message-ID: <179468100783.2330384.13747727141754933715.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261114051805.683966-1-alexei.starovoitov@gmail.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Sat, 14 Nov 2026 05:17:54 +0000 you wrote:
> From: Alexei Starovoitov <ast@kernel.org>
>
> In short: with CONFIG_BPF_FMODRET_SCAN=y the build tags the functions that
> return errors, 12096 of them. A program with CAP_BPF and CAP_PERFMON can
> attach to one, skip a call and return one of its errors. No file of net, fs
> or mm changes. Test: one skipped call per function, 4401 functions of net,
> fs, mm. With this set 1 function in 180 then damages the kernel. A deny
> list by name can take those out.
>
> [...]
Here is the summary with links:
- [v3,bpf-next,01/11] selftests/bpf: Don't depend on the width of a BTF id in verifier_live_stack
https://git.kernel.org/bpf/bpf-next/c/b44ccfb0c4fb
- [v3,bpf-next,02/11] resolve_btfids: Read the code of an ELF file by address
https://git.kernel.org/bpf/bpf-next/c/c7c875e1d0b6
- [v3,bpf-next,03/11] resolve_btfids: Describe machine instructions with LLVM's MC layer
https://git.kernel.org/bpf/bpf-next/c/59f3c4a33bb7
- [v3,bpf-next,04/11] resolve_btfids: Find the definitions that reach the return value
https://git.kernel.org/bpf/bpf-next/c/a9feed88f7bb
- [v3,bpf-next,05/11] resolve_btfids: Tag the functions that return errors
https://git.kernel.org/bpf/bpf-next/c/4dd950adacad
- [v3,bpf-next,06/11] resolve_btfids: Fold the constants of a select without a branch
https://git.kernel.org/bpf/bpf-next/c/6a2f944d0cde
- [v3,bpf-next,07/11] resolve_btfids: Say which registers an instruction reads
https://git.kernel.org/bpf/bpf-next/c/0ea8d17b993f
- [v3,bpf-next,08/11] resolve_btfids: Don't list an error that follows work on an argument
https://git.kernel.org/bpf/bpf-next/c/bfaa56d69ff6
- [v3,bpf-next,09/11] bpf: Allow fmod_ret on tagged functions and check the return value
https://git.kernel.org/bpf/bpf-next/c/bc45414d1690
- [v3,bpf-next,10/11] bpf: Require the JIT for fmod_ret programs on tagged 64-bit targets
https://git.kernel.org/bpf/bpf-next/c/3c5d146f9c69
- [v3,bpf-next,11/11] selftests/bpf: Test fmod_ret on tagged functions
https://git.kernel.org/bpf/bpf-next/c/e93e5df855f5
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-14 18:30 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-14 5:17 [PATCH v3 bpf-next 00/11] bpf: fmod_ret for each function that returns errors Alexei Starovoitov
2026-11-14 5:17 ` [PATCH v3 bpf-next 01/11] selftests/bpf: Don't depend on the width of a BTF id in verifier_live_stack Alexei Starovoitov
2026-11-14 5:17 ` [PATCH v3 bpf-next 02/11] resolve_btfids: Read the code of an ELF file by address Alexei Starovoitov
2026-11-14 5:17 ` [PATCH v3 bpf-next 03/11] resolve_btfids: Describe machine instructions with LLVM's MC layer Alexei Starovoitov
2026-11-14 5:17 ` [PATCH v3 bpf-next 04/11] resolve_btfids: Find the definitions that reach the return value Alexei Starovoitov
2026-11-14 5:17 ` [PATCH v3 bpf-next 05/11] resolve_btfids: Tag the functions that return errors Alexei Starovoitov
2026-11-14 6:05 ` bot+bpf-ci
2026-11-14 19:37 ` David Windsor
2026-11-14 20:00 ` Alexei Starovoitov
2026-11-14 5:18 ` [PATCH v3 bpf-next 06/11] resolve_btfids: Fold the constants of a select without a branch Alexei Starovoitov
2026-11-14 5:18 ` [PATCH v3 bpf-next 07/11] resolve_btfids: Say which registers an instruction reads Alexei Starovoitov
2026-11-14 5:18 ` [PATCH v3 bpf-next 08/11] resolve_btfids: Don't list an error that follows work on an argument Alexei Starovoitov
2026-11-14 6:05 ` bot+bpf-ci
2026-11-14 5:18 ` [PATCH v3 bpf-next 09/11] bpf: Allow fmod_ret on tagged functions and check the return value Alexei Starovoitov
2026-11-14 5:18 ` [PATCH v3 bpf-next 10/11] bpf: Require the JIT for fmod_ret programs on tagged 64-bit targets Alexei Starovoitov
2026-11-14 5:18 ` [PATCH v3 bpf-next 11/11] selftests/bpf: Test fmod_ret on tagged functions Alexei Starovoitov
2026-11-14 18: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=179468100783.2330384.13747727141754933715.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=a.s.protopopov@gmail.com \
--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.