From: Song Liu <song@kernel.org>
To: bpf@vger.kernel.org, fsverity@lists.linux.dev
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
martin.lau@kernel.org, kernel-team@meta.com, ebiggers@kernel.org,
tytso@mit.edu, roberto.sassu@huaweicloud.com, kpsingh@kernel.org,
vadfed@meta.com, Song Liu <song@kernel.org>
Subject: [PATCH bpf-next 0/3] bpf: __bpf_dynptr_data* and __str annotation
Date: Mon, 6 Nov 2023 20:57:22 -0800 [thread overview]
Message-ID: <20231107045725.2278852-1-song@kernel.org> (raw)
This set contains the first 3 patches of set [1]. Currently, [1] is waiting
for [3] to be merged to bpf-next tree. So send these 3 patches first to
unblock other works, such as [2]. This set is verified with new version of
[1] in CI run [4].
Changes since v12 of [1]:
1. Reuse bpf_dynptr_slice() in __bpf_dynptr_data(). (Andrii)
2. Add Acked-by from Vadim Fedorenko.
[1] https://lore.kernel.org/bpf/20231104001313.3538201-1-song@kernel.org/
[2] https://lore.kernel.org/bpf/20231031134900.1432945-1-vadfed@meta.com/
[3] https://lore.kernel.org/bpf/20231031215625.2343848-1-davemarchevsky@fb.com/
[4] https://github.com/kernel-patches/bpf/actions/runs/6779945063/job/18427926114
Song Liu (3):
bpf: Add __bpf_dynptr_data* for in kernel use
bpf: Factor out helper check_reg_const_str()
bpf: Introduce KF_ARG_PTR_TO_CONST_STR
Documentation/bpf/kfuncs.rst | 24 ++++++++
include/linux/bpf.h | 2 +
kernel/bpf/helpers.c | 19 +++++++
kernel/bpf/verifier.c | 104 +++++++++++++++++++++++------------
kernel/trace/bpf_trace.c | 12 ++--
5 files changed, 121 insertions(+), 40 deletions(-)
--
2.34.1
next reply other threads:[~2023-11-07 4:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-07 4:57 Song Liu [this message]
2023-11-07 4:57 ` [PATCH bpf-next 1/3] bpf: Add __bpf_dynptr_data* for in kernel use Song Liu
2023-11-07 4:57 ` [PATCH bpf-next 2/3] bpf: Factor out helper check_reg_const_str() Song Liu
2023-11-07 4:57 ` [PATCH bpf-next 3/3] bpf: Introduce KF_ARG_PTR_TO_CONST_STR Song Liu
2023-11-07 18:10 ` [PATCH bpf-next 0/3] bpf: __bpf_dynptr_data* and __str annotation patchwork-bot+netdevbpf
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=20231107045725.2278852-1-song@kernel.org \
--to=song@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=ebiggers@kernel.org \
--cc=fsverity@lists.linux.dev \
--cc=kernel-team@meta.com \
--cc=kpsingh@kernel.org \
--cc=martin.lau@kernel.org \
--cc=roberto.sassu@huaweicloud.com \
--cc=tytso@mit.edu \
--cc=vadfed@meta.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 read-only IMAP folder(s) and NNTP newsgroup(s).