From: bot+bpf-ci@kernel.org
To: alan.maguire@oracle.com,andrii@kernel.org,ast@kernel.org
Cc: daniel@iogearbox.net,martin.lau@linux.dev,eddyz87@gmail.com,song@kernel.org,yonghong.song@linux.dev,john.fastabend@gmail.com,kpsingh@kernel.org,sdf@fomichev.me,haoluo@google.com,jolsa@kernel.org,qmo@kernel.org,ihor.solodrai@linux.dev,dwarves@vger.kernel.org,bpf@vger.kernel.org,ttreyer@meta.com,alan.maguire@oracle.com,ast@kernel.org,andrii@kernel.org,daniel@iogearbox.net,martin.lau@kernel.org,eddyz87@gmail.com,yonghong.song@linux.dev,clm@meta.com,ihor.solodrai@linux.dev
Subject: Re: [PATCH v7 bpf-next 02/10] libbpf: Support kind layout section handling in BTF
Date: Thu, 11 Dec 2025 17:07:57 +0000 (UTC) [thread overview]
Message-ID: <c051f3dfd97b289e23bd9a04cb33f8ad8a40a425e7a5d4c98bf04329f74b7f33@mail.kernel.org> (raw)
In-Reply-To: <20251211164646.1219122-3-alan.maguire@oracle.com>
[-- Attachment #1: Type: text/plain, Size: 4623 bytes --]
> diff --git a/tools/lib/bpf/btf.c b/tools/lib/bpf/btf.c
> index b136572e889a..531089a64adc 100644
> --- a/tools/lib/bpf/btf.c
> +++ b/tools/lib/bpf/btf.c
[ ... ]
> @@ -214,7 +232,7 @@ static int btf_add_type_idx_entry(struct btf *btf, __u32 type_off)
> return 0;
> }
>
> -static void btf_bswap_hdr(struct btf_header *h)
> +static void btf_bswap_hdr(struct btf_header *h, __u32 hdr_len)
> {
> h->magic = bswap_16(h->magic);
> h->hdr_len = bswap_32(h->hdr_len);
> @@ -222,54 +240,89 @@ static void btf_bswap_hdr(struct btf_header *h)
> h->type_len = bswap_32(h->type_len);
> h->str_off = bswap_32(h->str_off);
> h->str_len = bswap_32(h->str_len);
> + /* May be operating on raw data with hdr_len that does not include below fields */
> + if (hdr_len >= sizeof(struct btf_header)) {
> + h->kind_layout_off = bswap_32(h->kind_layout_off);
> + h->kind_layout_len = bswap_32(h->kind_layout_len);
> + }
> }
>
> static int btf_parse_hdr(struct btf *btf)
> {
> - struct btf_header *hdr = btf->hdr;
> + struct btf_header *hdr = btf->raw_data;
> + __u32 hdr_len = hdr->hdr_len;
> __u32 meta_left;
>
> - if (btf->raw_size < sizeof(struct btf_header)) {
> + if (btf->raw_size < offsetofend(struct btf_header, str_len)) {
> pr_debug("BTF header not found\n");
> return -EINVAL;
> }
>
> if (hdr->magic == bswap_16(BTF_MAGIC)) {
> btf->swapped_endian = true;
> - if (bswap_32(hdr->hdr_len) != sizeof(struct btf_header)) {
> + hdr_len = bswap_32(hdr->hdr_len);
> + if (hdr_len < offsetofend(struct btf_header, str_len)) {
> pr_warn("Can't load BTF with non-native endianness due to unsupported header length %u\n",
> - bswap_32(hdr->hdr_len));
> + hdr_len);
> return -ENOTSUP;
> }
> - btf_bswap_hdr(hdr);
> } else if (hdr->magic != BTF_MAGIC) {
> pr_debug("Invalid BTF magic: %x\n", hdr->magic);
> return -EINVAL;
> }
>
> - if (btf->raw_size < hdr->hdr_len) {
> + if (btf->raw_size < hdr_len) {
> pr_debug("BTF header len %u larger than data size %u\n",
> - hdr->hdr_len, btf->raw_size);
> + hdr_len, btf->raw_size);
> return -EINVAL;
> }
>
> - meta_left = btf->raw_size - hdr->hdr_len;
> - if (meta_left < (long long)hdr->str_off + hdr->str_len) {
> + /* At this point, we have basic header information, so allocate btf->hdr */
> + btf->hdr = calloc(1, sizeof(struct btf_header));
> + if (!btf->hdr) {
> + pr_debug("BTF header allocation failed\n");
> + return -ENOMEM;
> + }
> + if (btf->swapped_endian)
> + btf_bswap_hdr(hdr, hdr_len);
^^^
Can this segfault on mmap'd BTF data? In btf_parse_raw_mmap(), the BTF
file is mmap'd with PROT_READ (read-only), then btf_new() is called with
is_mmap=true. The hdr pointer here points to btf->raw_data which is the
mmap'd read-only memory. When btf_bswap_hdr() attempts to write to hdr
(swapping the header fields in-place), it will write to read-only memory.
This differs from the old code which rejected swapped-endian BTF with
the old strict header size check. Now that the header size check is
relaxed to support kind layout, swapped-endian BTF from mmap becomes
accessible but crashes.
Call chain: btf__parse_raw()->btf_parse_raw_mmap() mmaps PROT_READ at
mmap() call, then btf_new(..., true) sets btf->raw_data to mmap'd
memory, then btf_parse_hdr() attempts to write to it.
> + memcpy(btf->hdr, hdr, hdr_len < sizeof(struct btf_header) ? hdr_len :
> + sizeof(struct btf_header));
[ ... ]
> @@ -1550,6 +1629,11 @@ static void *btf_get_raw_data(const struct btf *btf, __u32 *size, bool swap_endi
> }
>
> data_sz = hdr->hdr_len + hdr->type_len + hdr->str_len;
> + if (btf->kind_layout) {
> + data_sz = roundup(data_sz, 4);
> + data_sz += hdr->kind_layout_len;
> + hdr->kind_layout_off = roundup(hdr->type_len + hdr->str_len, 4);
^^^^^^^^^^^^^^^^^^^^
Should btf_get_raw_data() modify btf->hdr->kind_layout_off? The hdr
pointer is btf->hdr, so this modifies the BTF object's header. The
function signature takes const struct btf *btf_ro, suggesting the object
shouldn't be modified. If btf__raw_data() is called multiple times,
kind_layout_off could potentially be set to different values on each
call, or if the BTF was originally loaded with kind_layout at a
different offset, that information is lost.
> + }
> data = calloc(1, data_sz);
> if (!data)
> return NULL;
[ ... ]
---
AI reviewed your patch. Please fix the bug or email reply why it's not a bug.
See: https://github.com/kernel-patches/vmtest/blob/master/ci/claude/README.md
CI run summary: https://github.com/kernel-patches/bpf/actions/runs/20140850025
next prev parent reply other threads:[~2025-12-11 17:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-11 16:46 [PATCH v7 bpf-next 00/10] Add kind layout to BTF Alan Maguire
2025-12-11 16:46 ` [PATCH v7 bpf-next 01/10] btf: add kind layout encoding to UAPI Alan Maguire
2025-12-11 16:46 ` [PATCH v7 bpf-next 02/10] libbpf: Support kind layout section handling in BTF Alan Maguire
2025-12-11 17:07 ` bot+bpf-ci [this message]
2025-12-11 16:46 ` [PATCH v7 bpf-next 03/10] libbpf: use kind layout to compute an unknown kind size Alan Maguire
2025-12-11 16:46 ` [PATCH v7 bpf-next 04/10] libbpf: Add kind layout encoding support Alan Maguire
2025-12-11 16:46 ` [PATCH v7 bpf-next 05/10] libbpf: BTF validation can use kind layout for unknown kinds Alan Maguire
2025-12-11 16:46 ` [PATCH v7 bpf-next 06/10] btf: support kernel parsing of BTF with kind layout Alan Maguire
2025-12-11 17:08 ` bot+bpf-ci
2025-12-11 16:46 ` [PATCH v7 bpf-next 07/10] selftests/bpf: test kind encoding/decoding Alan Maguire
2025-12-11 16:46 ` [PATCH v7 bpf-next 08/10] bpftool: add BTF dump "format meta" to dump header/metadata Alan Maguire
2025-12-11 16:46 ` [PATCH v7 bpf-next 09/10] bpftool: Update doc to describe bpftool btf dump .. format metadata Alan Maguire
2025-12-11 16:46 ` [PATCH v7 bpf-next 10/10] kbuild, bpf: Specify "kind_layout" optional feature 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=c051f3dfd97b289e23bd9a04cb33f8ad8a40a425e7a5d4c98bf04329f74b7f33@mail.kernel.org \
--to=bot+bpf-ci@kernel.org \
--cc=alan.maguire@oracle.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=clm@meta.com \
--cc=daniel@iogearbox.net \
--cc=dwarves@vger.kernel.org \
--cc=eddyz87@gmail.com \
--cc=haoluo@google.com \
--cc=ihor.solodrai@linux.dev \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=martin.lau@kernel.org \
--cc=martin.lau@linux.dev \
--cc=qmo@kernel.org \
--cc=sdf@fomichev.me \
--cc=song@kernel.org \
--cc=ttreyer@meta.com \
--cc=yonghong.song@linux.dev \
/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).