From: patchwork-bot+netdevbpf@kernel.org
To: Kumar Kartikeya Dwivedi <memxor@gmail.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
andrii@kernel.org, kafai@fb.com
Subject: Re: [PATCH bpf-next v4 0/8] Fixes for bad PTR_TO_BTF_ID offset
Date: Sat, 05 Mar 2022 23:40:11 +0000 [thread overview]
Message-ID: <164652361197.32325.912382590495519360.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220304224645.3677453-1-memxor@gmail.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Sat, 5 Mar 2022 04:16:37 +0530 you wrote:
> This set fixes a bug related to bad var_off being permitted for kfunc call in
> case of PTR_TO_BTF_ID, consolidates offset checks for all register types allowed
> as helper or kfunc arguments into a common shared helper, and introduces a
> couple of other checks to harden the kfunc release logic and prevent future
> bugs. Some selftests are also included that fail in absence of these fixes,
> serving as demonstration of the issues being fixed.
>
> [...]
Here is the summary with links:
- [bpf-next,v4,1/8] bpf: Add check_func_arg_reg_off function
https://git.kernel.org/bpf/bpf-next/c/25b35dd28138
- [bpf-next,v4,2/8] bpf: Fix PTR_TO_BTF_ID var_off check
https://git.kernel.org/bpf/bpf-next/c/655efe5089f0
- [bpf-next,v4,3/8] bpf: Disallow negative offset in check_ptr_off_reg
https://git.kernel.org/bpf/bpf-next/c/e1fad0ff46b3
- [bpf-next,v4,4/8] bpf: Harden register offset checks for release helpers and kfuncs
https://git.kernel.org/bpf/bpf-next/c/24d5bb806c7e
- [bpf-next,v4,5/8] compiler-clang.h: Add __diag infrastructure for clang
https://git.kernel.org/bpf/bpf-next/c/f014a00bbeb0
- [bpf-next,v4,6/8] compiler_types.h: Add unified __diag_ignore_all for GCC/LLVM
https://git.kernel.org/bpf/bpf-next/c/4d1ea705d797
- [bpf-next,v4,7/8] bpf: Replace __diag_ignore with unified __diag_ignore_all
https://git.kernel.org/bpf/bpf-next/c/0b206c6d1066
- [bpf-next,v4,8/8] selftests/bpf: Add tests for kfunc register offset checks
https://git.kernel.org/bpf/bpf-next/c/8218ccb5bd68
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:[~2022-03-05 23:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-04 22:46 [PATCH bpf-next v4 0/8] Fixes for bad PTR_TO_BTF_ID offset Kumar Kartikeya Dwivedi
2022-03-04 22:46 ` [PATCH bpf-next v4 1/8] bpf: Add check_func_arg_reg_off function Kumar Kartikeya Dwivedi
2022-03-04 22:46 ` [PATCH bpf-next v4 2/8] bpf: Fix PTR_TO_BTF_ID var_off check Kumar Kartikeya Dwivedi
2022-03-04 22:46 ` [PATCH bpf-next v4 3/8] bpf: Disallow negative offset in check_ptr_off_reg Kumar Kartikeya Dwivedi
2022-03-04 22:46 ` [PATCH bpf-next v4 4/8] bpf: Harden register offset checks for release helpers and kfuncs Kumar Kartikeya Dwivedi
2022-03-04 22:46 ` [PATCH bpf-next v4 5/8] compiler-clang.h: Add __diag infrastructure for clang Kumar Kartikeya Dwivedi
2022-03-07 19:25 ` Nick Desaulniers
2022-03-07 19:27 ` Nick Desaulniers
2022-03-07 20:50 ` Kumar Kartikeya Dwivedi
2022-03-04 22:46 ` [PATCH bpf-next v4 6/8] compiler_types.h: Add unified __diag_ignore_all for GCC/LLVM Kumar Kartikeya Dwivedi
2022-03-07 19:30 ` Nick Desaulniers
2022-03-07 20:51 ` Kumar Kartikeya Dwivedi
2022-03-04 22:46 ` [PATCH bpf-next v4 7/8] bpf: Replace __diag_ignore with unified __diag_ignore_all Kumar Kartikeya Dwivedi
2022-03-04 22:46 ` [PATCH bpf-next v4 8/8] selftests/bpf: Add tests for kfunc register offset checks Kumar Kartikeya Dwivedi
2022-03-04 23:26 ` [PATCH bpf-next v4 0/8] Fixes for bad PTR_TO_BTF_ID offset Martin KaFai Lau
2022-03-05 23: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=164652361197.32325.912382590495519360.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=kafai@fb.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.