From: Andrii Nakryiko <andrii.nakryiko@gmail.com>
To: Alan Maguire <alan.maguire@oracle.com>
Cc: acme@kernel.org, ast@kernel.org, andrii@kernel.org,
daniel@iogearbox.net, quentin@isovalent.com, jolsa@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, mykolal@fb.com, bpf@vger.kernel.org
Subject: Re: [PATCH v2 bpf-next 4/9] btf: support kernel parsing of BTF with kind layout
Date: Thu, 22 Jun 2023 15:03:21 -0700 [thread overview]
Message-ID: <CAEf4BzbKaZm-STb3USz=T9jhtK+=TtFK_cpcoJfZ7rxqt=9TRA@mail.gmail.com> (raw)
In-Reply-To: <20230616171728.530116-5-alan.maguire@oracle.com>
On Fri, Jun 16, 2023 at 10:18 AM Alan Maguire <alan.maguire@oracle.com> wrote:
>
> Use kind layout to parse BTF with unknown kinds that have a
> kind layout representation.
>
> Validate kind layout if present, and use it to parse BTF with
> unrecognized kinds. Reject BTF that contains a type
> of a kind that is not optional.
>
> Signed-off-by: Alan Maguire <alan.maguire@oracle.com>
> ---
> kernel/bpf/btf.c | 102 +++++++++++++++++++++++++++++++++++++----------
> 1 file changed, 82 insertions(+), 20 deletions(-)
>
> diff --git a/kernel/bpf/btf.c b/kernel/bpf/btf.c
> index bd2cac057928..ffe3926ea051 100644
> --- a/kernel/bpf/btf.c
> +++ b/kernel/bpf/btf.c
> @@ -257,6 +257,7 @@ struct btf {
> struct btf_kfunc_set_tab *kfunc_set_tab;
> struct btf_id_dtor_kfunc_tab *dtor_kfunc_tab;
> struct btf_struct_metas *struct_meta_tab;
> + struct btf_kind_layout *kind_layout;
>
> /* split BTF support */
> struct btf *base_btf;
> @@ -4965,22 +4966,41 @@ static s32 btf_check_meta(struct btf_verifier_env *env,
> return -EINVAL;
> }
>
> - if (BTF_INFO_KIND(t->info) > BTF_KIND_MAX ||
> - BTF_INFO_KIND(t->info) == BTF_KIND_UNKN) {
> - btf_verifier_log(env, "[%u] Invalid kind:%u",
> - env->log_type_id, BTF_INFO_KIND(t->info));
> - return -EINVAL;
> - }
> -
> if (!btf_name_offset_valid(env->btf, t->name_off)) {
> btf_verifier_log(env, "[%u] Invalid name_offset:%u",
> env->log_type_id, t->name_off);
> return -EINVAL;
> }
>
> - var_meta_size = btf_type_ops(t)->check_meta(env, t, meta_left);
> - if (var_meta_size < 0)
> - return var_meta_size;
> + if (BTF_INFO_KIND(t->info) == BTF_KIND_UNKN) {
> + btf_verifier_log(env, "[%u] Invalid kind:%u",
> + env->log_type_id, BTF_INFO_KIND(t->info));
> + return -EINVAL;
> + }
> +
> + if (BTF_INFO_KIND(t->info) > BTF_KIND_MAX && env->btf->kind_layout &&
> + (BTF_INFO_KIND(t->info) * sizeof(struct btf_kind_layout)) <
> + env->btf->hdr.kind_layout_len) {
> + struct btf_kind_layout *k = &env->btf->kind_layout[BTF_INFO_KIND(t->info)];
> +
> + if (!(k->flags & BTF_KIND_LAYOUT_OPTIONAL)) {
same question as on previous patch, should kernel trust and handle
OPTIONAL flag?
I'd say let's drop it for now, doesn't seem worth the trouble
> + btf_verifier_log(env, "[%u] unknown but required kind %u",
> + env->log_type_id,
> + BTF_INFO_KIND(t->info));
> + return -EINVAL;
> + }
> + var_meta_size = sizeof(struct btf_type);
> + var_meta_size += k->info_sz + (btf_type_vlen(t) * k->elem_sz);
> + } else {
> + if (BTF_INFO_KIND(t->info) > BTF_KIND_MAX) {
> + btf_verifier_log(env, "[%u] Invalid kind:%u",
> + env->log_type_id, BTF_INFO_KIND(t->info));
> + return -EINVAL;
> + }
> + var_meta_size = btf_type_ops(t)->check_meta(env, t, meta_left);
> + if (var_meta_size < 0)
> + return var_meta_size;
> + }
>
> meta_left -= var_meta_size;
>
> @@ -5155,7 +5175,8 @@ static int btf_parse_str_sec(struct btf_verifier_env *env)
> start = btf->nohdr_data + hdr->str_off;
> end = start + hdr->str_len;
>
> - if (end != btf->data + btf->data_size) {
> + if (hdr->hdr_len < sizeof(struct btf_header) &&
> + end != btf->data + btf->data_size) {
> btf_verifier_log(env, "String section is not at the end");
> return -EINVAL;
> }
> @@ -5176,9 +5197,41 @@ static int btf_parse_str_sec(struct btf_verifier_env *env)
> return 0;
> }
>
> +static int btf_parse_kind_layout_sec(struct btf_verifier_env *env)
> +{
> + const struct btf_header *hdr = &env->btf->hdr;
> + struct btf *btf = env->btf;
> + void *start, *end;
> +
> + if (hdr->hdr_len < sizeof(struct btf_header) ||
> + hdr->kind_layout_len == 0)
let's make sure that kind_layout_off is zero in this case as well
> + return 0;
> +
> + /* Kind layout section must align to 4 bytes */
> + if (hdr->kind_layout_off & (sizeof(u32) - 1)) {
> + btf_verifier_log(env, "Unaligned kind_layout_off");
> + return -EINVAL;
> + }
> + start = btf->nohdr_data + hdr->kind_layout_off;
> + end = start + hdr->kind_layout_len;
> +
> + if (hdr->kind_layout_len < sizeof(struct btf_kind_layout)) {
same as on libbpf side, more generally kind_layout_len should be a
multiple of sizeof(struct btf_kind_layout)
> + btf_verifier_log(env, "Kind layout section is too small");
> + return -EINVAL;
> + }
> + if (end != btf->data + btf->data_size) {
> + btf_verifier_log(env, "Kind layout section is not at the end");
> + return -EINVAL;
> + }
> + btf->kind_layout = start;
> +
> + return 0;
> +}
> +
[...]
next prev parent reply other threads:[~2023-06-22 22:03 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-16 17:17 [PATCH v2 bpf-next 0/9] bpf: support BTF kind layout info, CRCs Alan Maguire
2023-06-16 17:17 ` [PATCH v2 bpf-next 1/9] btf: add kind layout encoding, crcs to UAPI Alan Maguire
2023-06-17 0:39 ` Alexei Starovoitov
2023-06-22 22:02 ` Andrii Nakryiko
2023-07-03 13:42 ` Alan Maguire
2023-07-05 23:48 ` Andrii Nakryiko
2023-07-20 20:18 ` Alan Maguire
2023-06-16 17:17 ` [PATCH v2 bpf-next 2/9] libbpf: support handling of kind layout section in BTF Alan Maguire
2023-06-22 22:02 ` Andrii Nakryiko
2023-06-16 17:17 ` [PATCH v2 bpf-next 3/9] libbpf: use kind layout to compute an unknown kind size Alan Maguire
2023-06-22 22:03 ` Andrii Nakryiko
2023-06-16 17:17 ` [PATCH v2 bpf-next 4/9] btf: support kernel parsing of BTF with kind layout Alan Maguire
2023-06-18 13:08 ` Jiri Olsa
2023-06-20 8:40 ` Alan Maguire
2023-06-22 22:03 ` Andrii Nakryiko [this message]
2023-06-16 17:17 ` [PATCH v2 bpf-next 5/9] libbpf: add kind layout encoding, crc support Alan Maguire
2023-06-19 23:24 ` Yonghong Song
2023-06-20 9:09 ` Alan Maguire
2023-06-20 14:41 ` Yonghong Song
2023-06-22 22:04 ` Andrii Nakryiko
2023-06-16 17:17 ` [PATCH v2 bpf-next 6/9] btf: generate BTF kind layout for vmlinux/module BTF Alan Maguire
2023-06-16 18:53 ` kernel test robot
2023-06-18 13:07 ` Jiri Olsa
2023-06-20 8:46 ` Alan Maguire
2023-06-16 17:17 ` [PATCH v2 bpf-next 7/9] bpftool: add BTF dump "format meta" to dump header/metadata Alan Maguire
2023-06-22 22:04 ` Andrii Nakryiko
2023-06-29 14:16 ` Quentin Monnet
2023-06-16 17:17 ` [PATCH v2 bpf-next 8/9] bpftool: update doc to describe bpftool btf dump .. format meta Alan Maguire
2023-06-29 14:16 ` Quentin Monnet
2023-06-16 17:17 ` [PATCH v2 bpf-next 9/9] selftests/bpf: test kind encoding/decoding Alan Maguire
2023-06-22 23:48 ` Andrii Nakryiko
2023-06-16 17:17 ` [PATCH dwarves] dwarves: encode BTF kind layout, crcs Alan Maguire
2023-06-17 0:39 ` [PATCH v2 bpf-next 0/9] bpf: support BTF kind layout info, CRCs Alexei Starovoitov
2023-06-20 8:41 ` Alan Maguire
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='CAEf4BzbKaZm-STb3USz=T9jhtK+=TtFK_cpcoJfZ7rxqt=9TRA@mail.gmail.com' \
--to=andrii.nakryiko@gmail.com \
--cc=acme@kernel.org \
--cc=alan.maguire@oracle.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=martin.lau@linux.dev \
--cc=mykolal@fb.com \
--cc=quentin@isovalent.com \
--cc=sdf@google.com \
--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).