From: patchwork-bot+netdevbpf@kernel.org
To: Roberto Sassu <roberto.sassu@huaweicloud.com>
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
martin.lau@linux.dev, song@kernel.org, yhs@fb.com,
john.fastabend@gmail.com, kpsingh@kernel.org, sdf@google.com,
haoluo@google.com, jolsa@kernel.org, mykolal@fb.com,
dhowells@redhat.com, jarkko@kernel.org, rostedt@goodmis.org,
mingo@redhat.com, paul@paul-moore.com, jmorris@namei.org,
serge@hallyn.com, shuah@kernel.org, bpf@vger.kernel.org,
keyrings@vger.kernel.org, linux-security-module@vger.kernel.org,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org,
deso@posteo.net, memxor@gmail.com, roberto.sassu@huawei.com
Subject: Re: [PATCH v18 00/13] bpf: Add kfuncs for PKCS#7 signature verification
Date: Thu, 22 Sep 2022 01:10:19 +0000 [thread overview]
Message-ID: <166380901992.22214.9738927038585872619.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220920075951.929132-1-roberto.sassu@huaweicloud.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Tue, 20 Sep 2022 09:59:38 +0200 you wrote:
> From: Roberto Sassu <roberto.sassu@huawei.com>
>
> One of the desirable features in security is the ability to restrict import
> of data to a given system based on data authenticity. If data import can be
> restricted, it would be possible to enforce a system-wide policy based on
> the signing keys the system owner trusts.
>
> [...]
Here is the summary with links:
- [v18,01/13] bpf: Allow kfuncs to be used in LSM programs
https://git.kernel.org/bpf/bpf-next/c/d15bf1501c75
- [v18,02/13] btf: Export bpf_dynptr definition
https://git.kernel.org/bpf/bpf-next/c/00f146413ccb
- [v18,03/13] bpf: Move dynptr type check to is_dynptr_type_expected()
https://git.kernel.org/bpf/bpf-next/c/e9e315b4a5de
- [v18,04/13] btf: Allow dynamic pointer parameters in kfuncs
https://git.kernel.org/bpf/bpf-next/c/b8d31762a0ae
- [v18,05/13] bpf: Export bpf_dynptr_get_size()
https://git.kernel.org/bpf/bpf-next/c/51df48657185
- [v18,06/13] KEYS: Move KEY_LOOKUP_ to include/linux/key.h and define KEY_LOOKUP_ALL
https://git.kernel.org/bpf/bpf-next/c/90fd8f26edd4
- [v18,07/13] bpf: Add bpf_lookup_*_key() and bpf_key_put() kfuncs
https://git.kernel.org/bpf/bpf-next/c/f3cf4134c5c6
- [v18,08/13] bpf: Add bpf_verify_pkcs7_signature() kfunc
https://git.kernel.org/bpf/bpf-next/c/865b0566d8f1
- [v18,09/13] selftests/bpf: Compile kernel with everything as built-in
https://git.kernel.org/bpf/bpf-next/c/94fd7420faa0
- [v18,10/13] selftests/bpf: Add verifier tests for bpf_lookup_*_key() and bpf_key_put()
https://git.kernel.org/bpf/bpf-next/c/7c036ed9e006
- [v18,11/13] selftests/bpf: Add additional tests for bpf_lookup_*_key()
https://git.kernel.org/bpf/bpf-next/c/ecce368d6e6d
- [v18,12/13] selftests/bpf: Add test for bpf_verify_pkcs7_signature() kfunc
https://git.kernel.org/bpf/bpf-next/c/fc97590668ae
- [v18,13/13] selftests/bpf: Add tests for dynamic pointers parameters in kfuncs
https://git.kernel.org/bpf/bpf-next/c/b94fa9f9dcf9
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-09-22 1:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-20 7:59 [PATCH v18 00/13] bpf: Add kfuncs for PKCS#7 signature verification Roberto Sassu
2022-09-20 7:59 ` [PATCH v18 01/13] bpf: Allow kfuncs to be used in LSM programs Roberto Sassu
2022-09-20 7:59 ` [PATCH v18 02/13] btf: Export bpf_dynptr definition Roberto Sassu
2022-09-21 13:43 ` KP Singh
2022-09-20 7:59 ` [PATCH v18 03/13] bpf: Move dynptr type check to is_dynptr_type_expected() Roberto Sassu
2022-09-20 7:59 ` [PATCH v18 04/13] btf: Allow dynamic pointer parameters in kfuncs Roberto Sassu
2022-09-20 7:59 ` [PATCH v18 05/13] bpf: Export bpf_dynptr_get_size() Roberto Sassu
2022-09-20 7:59 ` [PATCH v18 06/13] KEYS: Move KEY_LOOKUP_ to include/linux/key.h and define KEY_LOOKUP_ALL Roberto Sassu
2022-09-20 7:59 ` [PATCH v18 07/13] bpf: Add bpf_lookup_*_key() and bpf_key_put() kfuncs Roberto Sassu
2022-09-20 7:59 ` [PATCH v18 08/13] bpf: Add bpf_verify_pkcs7_signature() kfunc Roberto Sassu
2022-09-20 7:59 ` [PATCH v18 09/13] selftests/bpf: Compile kernel with everything as built-in Roberto Sassu
2022-09-20 7:59 ` [PATCH v18 10/13] selftests/bpf: Add verifier tests for bpf_lookup_*_key() and bpf_key_put() Roberto Sassu
2022-09-20 7:59 ` [PATCH v18 11/13] selftests/bpf: Add additional tests for bpf_lookup_*_key() Roberto Sassu
2022-09-20 7:59 ` [PATCH v18 12/13] selftests/bpf: Add test for bpf_verify_pkcs7_signature() kfunc Roberto Sassu
2022-09-20 7:59 ` [PATCH v18 13/13] selftests/bpf: Add tests for dynamic pointers parameters in kfuncs Roberto Sassu
2022-09-22 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=166380901992.22214.9738927038585872619.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=deso@posteo.net \
--cc=dhowells@redhat.com \
--cc=haoluo@google.com \
--cc=jarkko@kernel.org \
--cc=jmorris@namei.org \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=keyrings@vger.kernel.org \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=memxor@gmail.com \
--cc=mingo@redhat.com \
--cc=mykolal@fb.com \
--cc=paul@paul-moore.com \
--cc=roberto.sassu@huawei.com \
--cc=roberto.sassu@huaweicloud.com \
--cc=rostedt@goodmis.org \
--cc=sdf@google.com \
--cc=serge@hallyn.com \
--cc=shuah@kernel.org \
--cc=song@kernel.org \
--cc=yhs@fb.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;
as well as URLs for NNTP newsgroup(s).