From: KP Singh <kpsingh@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, sdf@google.com, haoluo@google.com,
jolsa@kernel.org, mykolal@fb.com, corbet@lwn.net,
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,
linux-doc@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, Roberto Sassu <roberto.sassu@huawei.com>,
Joanne Koong <joannelkoong@gmail.com>
Subject: Re: [PATCH v13 03/10] bpf: Export bpf_dynptr_get_size()
Date: Sun, 28 Aug 2022 01:33:23 +0200 [thread overview]
Message-ID: <CACYkzJ7esNWFHTXF+sW8rgFDtKdPNfePoXQ_xnzP7eQipjKkXw@mail.gmail.com> (raw)
In-Reply-To: <20220823150035.711534-4-roberto.sassu@huaweicloud.com>
On Tue, Aug 23, 2022 at 5:02 PM Roberto Sassu
<roberto.sassu@huaweicloud.com> wrote:
>
> From: Roberto Sassu <roberto.sassu@huawei.com>
>
> Export bpf_dynptr_get_size(), so that kernel code dealing with eBPF dynamic
> pointers can obtain the real size of data carried by this data structure.
>
> Reviewed-by: Joanne Koong <joannelkoong@gmail.com>
> Signed-off-by: Roberto Sassu <roberto.sassu@huawei.com>
Acked-by: KP Singh <kpsingh@kernel.org>
next prev parent reply other threads:[~2022-08-27 23:33 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-23 15:00 [PATCH v13 00/10] bpf: Add kfuncs for PKCS#7 signature verification Roberto Sassu
2022-08-23 15:00 ` [PATCH v13 01/10] bpf: Allow kfuncs to be used in LSM programs Roberto Sassu
2022-08-23 15:00 ` [PATCH v13 02/10] btf: Handle dynamic pointer parameter in kfuncs Roberto Sassu
2022-08-26 20:36 ` Kumar Kartikeya Dwivedi
2022-08-23 15:00 ` [PATCH v13 03/10] bpf: Export bpf_dynptr_get_size() Roberto Sassu
2022-08-27 23:33 ` KP Singh [this message]
2022-08-23 15:00 ` [PATCH v13 04/10] KEYS: Move KEY_LOOKUP_ to include/linux/key.h Roberto Sassu
2022-08-23 15:00 ` [PATCH v13 05/10] bpf: Add bpf_lookup_*_key() and bpf_key_put() kfuncs Roberto Sassu
2022-08-26 5:56 ` Song Liu
2022-08-26 7:21 ` Roberto Sassu
2022-08-26 7:25 ` Song Liu
2022-08-26 7:31 ` Roberto Sassu
2022-08-23 15:00 ` [PATCH v13 06/10] bpf: Add bpf_verify_pkcs7_signature() kfunc Roberto Sassu
2022-08-23 15:00 ` [PATCH v13 07/10] selftests/bpf: Compile kernel with everything as built-in Roberto Sassu
2022-08-23 15:00 ` [PATCH v13 08/10] selftests/bpf: Add verifier tests for bpf_lookup_*_key() and bpf_key_put() Roberto Sassu
2022-08-23 15:00 ` [PATCH v13 09/10] selftests/bpf: Add additional tests for bpf_lookup_*_key() Roberto Sassu
2022-08-23 15:00 ` [PATCH v13 10/10] selftests/bpf: Add test for bpf_verify_pkcs7_signature() kfunc Roberto Sassu
2022-08-25 9:19 ` [PATCH v13 00/10] bpf: Add kfuncs for PKCS#7 signature verification Roberto Sassu
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=CACYkzJ7esNWFHTXF+sW8rgFDtKdPNfePoXQ_xnzP7eQipjKkXw@mail.gmail.com \
--to=kpsingh@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=corbet@lwn.net \
--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=joannelkoong@gmail.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=keyrings@vger.kernel.org \
--cc=linux-doc@vger.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=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).