From: Vineet Gupta <vineet.gupta@linux.dev>
To: Ihor Solodrai <ihor.solodrai@linux.dev>,
Alexei Starovoitov <ast@kernel.org>,
Andrii Nakryiko <andrii@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Eduard Zingerman <eddyz87@gmail.com>,
Kumar Kartikeya Dwivedi <memxor@gmail.com>,
Quentin Monnet <qmo@kernel.org>
Cc: bpf@vger.kernel.org, Alan Maguire <alan.maguire@oracle.com>,
Cupertino Miranda <cupertino.miranda@oracle.com>,
Ian Rogers <irogers@google.com>,
"Jose E . Marchesi" <jose.marchesi@oracle.com>,
Yonghong Song <yonghong.song@linux.dev>,
David Faust <david.faust@oss.qualcomm.com>
Subject: Re: [PATCH bpf-next v2 0/8] bpftool: Per-record CO-RE attributes in the C dump
Date: Fri, 23 Oct 2026 15:28:45 -0700 [thread overview]
Message-ID: <5225ee82-984b-4150-918c-bb6b9a05096c@linux.dev> (raw)
In-Reply-To: <20261023222652.3927736-1-ihor.solodrai@linux.dev>
+CC David's new email
On 10/23/26 3:26 PM, Ihor Solodrai wrote:
> bpftool's C dump wraps its output in a clang attribute pragma:
>
> #pragma clang attribute push (__attribute__((preserve_access_index)), apply_to = record)
>
> GCC-BPF implements preserve_access_index, but not the pragma. Since
> the commit 675b4e24bc50 ("bpf: Temporarily define
> BPF_NO_PRESEVE_ACCESS_INDEX for GCC") the BPF selftests build GCC
> objects with -DBPF_NO_PRESERVE_ACCESS_INDEX, which drops CO-RE from
> vmlinux.h altogether.
>
> This series replaces the pragma with an explicit attribute on each
> record definition, and uses the same mechanism to annotate the context
> types that the verifier rewrites with preserve_static_offset.
>
> Jose proposed per-record attributes in May 2024 [1]. It stalled on a
> requirement from preserve_static_offset (PSO) work [2] to add
> attributes on selected types only, which a fixed string cannot
> express.
>
> BTF decl tags can carry an arbitrary attribute list since commit
> 51d1b1d42841 ("libbpf: Introduce kflag for type_tags and decl_tags in
> BTF"), and btf_dump renders them on record definitions, since
> 76ea31239021 ("libbpf: Render decl_tags in btf_dump"). This allows
> bpftool to put any attribute on any subset of records, with no new
> libbpf API.
>
> [1] https://lore.kernel.org/bpf/20240503111836.25275-1-jose.marchesi@oracle.com/
> [2] https://lore.kernel.org/bpf/20231208000531.19179-1-eddyz87@gmail.com/
>
> ---
>
> v1->v2:
> * Rename __bpf_core_pai to __bpf_relocatable
> * Rename __bpf_core_pso to __bpf_static_offset
> * Use a split BTF to add decl_tags in bpftoo instead of a detached
> copy (Alexei, Alan)
> * New patch "libbpf: Look up BTF strings without making BTF
> modifiable" lets btf__find_str() build its string index without
> making BTF modifiable
> * Dropped patch "bpftool: Dump C from a detached BTF copy"
> * The Clang crash on __builtin_preserve_field_info over PSO types is
> fixed in LLVM. PSO stays on by default; -D__bpf_static_offset=
> remains the documented workaround for Clang 18 through 23
> * GCC-BPF gets __bpf_relocatable from patch #3, so its narrow loads
> from context types fail verification until patch #4 (bpf-ci bot),
> left as is
> * Commit message and documentation rewording
> v1: https://lore.kernel.org/bpf/20261016000012.2232059-1-ihor.solodrai@linux.dev/
>
> ---
>
> Ihor Solodrai (8):
> libbpf: Look up BTF strings without making BTF modifiable
> selftests/bpf: Cover unknown BTF header-extension bytes in btf dump
> bpftool: Apply __bpf_relocatable per record on BTF dump
> bpftool: Skip __bpf_relocatable on verifier-rewritten context types
> bpftool: Emit __bpf_static_offset on verifier-rewritten context types
> selftests/bpf: Cover record attributes in bpftool BTF dumps
> selftests/bpf: Cover context and socket accesses through vmlinux.h
> bpftool: Document __bpf_relocatable and __bpf_static_offset
>
> .../bpf/bpftool/Documentation/bpftool-btf.rst | 24 +++
> tools/bpf/bpftool/btf.c | 154 ++++++++++++++++--
> tools/lib/bpf/btf.c | 36 ++--
> .../bpf/bpftool_btf_dump_sorted.expected | 48 +++++-
> .../bpf/bpftool_btf_dump_unsorted.expected | 48 +++++-
> .../bpf/prog_tests/bpftool_btf_dump.c | 102 +++++++++++-
> .../selftests/bpf/prog_tests/verifier.c | 2 +
> .../bpf/progs/verifier_ctx_rewritten.c | 59 +++++++
> 8 files changed, 423 insertions(+), 50 deletions(-)
> create mode 100644 tools/testing/selftests/bpf/progs/verifier_ctx_rewritten.c
>
>
> base-commit: b116ac6087541d3d98031e786adbe9c733cd6df3
prev parent reply other threads:[~2026-10-23 22:28 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-23 22:26 [PATCH bpf-next v2 0/8] bpftool: Per-record CO-RE attributes in the C dump Ihor Solodrai
2026-10-23 22:26 ` [PATCH bpf-next v2 1/8] libbpf: Look up BTF strings without making BTF modifiable Ihor Solodrai
2026-10-23 22:39 ` sashiko-bot
2026-10-23 22:26 ` [PATCH bpf-next v2 2/8] selftests/bpf: Cover unknown BTF header-extension bytes in btf dump Ihor Solodrai
2026-10-23 22:26 ` [PATCH bpf-next v2 3/8] bpftool: Apply __bpf_relocatable per record on BTF dump Ihor Solodrai
2026-10-27 18:03 ` Andrii Nakryiko
2026-10-27 18:15 ` Ihor Solodrai
2026-10-27 18:21 ` Andrii Nakryiko
2026-10-27 18:26 ` Ihor Solodrai
2026-10-27 21:25 ` Ihor Solodrai
2026-10-23 22:26 ` [PATCH bpf-next v2 4/8] bpftool: Skip __bpf_relocatable on verifier-rewritten context types Ihor Solodrai
2026-10-27 18:06 ` Andrii Nakryiko
2026-10-27 18:10 ` Andrii Nakryiko
2026-10-27 18:17 ` Ihor Solodrai
2026-10-23 22:26 ` [PATCH bpf-next v2 5/8] bpftool: Emit __bpf_static_offset " Ihor Solodrai
2026-10-27 18:10 ` Andrii Nakryiko
2026-10-23 22:26 ` [PATCH bpf-next v2 6/8] selftests/bpf: Cover record attributes in bpftool BTF dumps Ihor Solodrai
2026-10-23 22:26 ` [PATCH bpf-next v2 7/8] selftests/bpf: Cover context and socket accesses through vmlinux.h Ihor Solodrai
2026-10-23 22:26 ` [PATCH bpf-next v2 8/8] bpftool: Document __bpf_relocatable and __bpf_static_offset Ihor Solodrai
2026-10-23 22:28 ` Vineet Gupta [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=5225ee82-984b-4150-918c-bb6b9a05096c@linux.dev \
--to=vineet.gupta@linux.dev \
--cc=alan.maguire@oracle.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=cupertino.miranda@oracle.com \
--cc=daniel@iogearbox.net \
--cc=david.faust@oss.qualcomm.com \
--cc=eddyz87@gmail.com \
--cc=ihor.solodrai@linux.dev \
--cc=irogers@google.com \
--cc=jose.marchesi@oracle.com \
--cc=memxor@gmail.com \
--cc=qmo@kernel.org \
--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