From: patchwork-bot+netdevbpf@kernel.org
To: Ihor Solodrai <ihor.solodrai@linux.dev>
Cc: ast@kernel.org, andrii@kernel.org, daniel@iogearbox.net,
eddyz87@gmail.com, memxor@gmail.com, qmo@kernel.org,
bpf@vger.kernel.org, alan.maguire@oracle.com,
cupertino.miranda@oracle.com, david.faust@oss.qualcomm.com,
irogers@google.com, jose.marchesi@oracle.com,
vineet.gupta@linux.dev, yonghong.song@linux.dev
Subject: Re: [PATCH bpf-next v4 00/17] bpftool: Per-record CO-RE attributes in the C dump
Date: Fri, 06 Nov 2026 00:30:09 +0000 [thread overview]
Message-ID: <179392500918.256564.14359701625669388609.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261105175845.30357-1-ihor.solodrai@linux.dev>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:
On Thu, 5 Nov 2026 10:58:28 -0700 you 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 disables automatic
> CO-RE for vmlinux.h field accesses.
>
> [...]
Here is the summary with links:
- [bpf-next,v4,01/17] Revert "libbpf: Render the arena type tag with its address space"
https://git.kernel.org/bpf/bpf-next/c/be5adbb5dbe7
- [bpf-next,v4,02/17] libbpf: Look up BTF strings without making BTF modifiable
https://git.kernel.org/bpf/bpf-next/c/efeb5ab5753d
- [bpf-next,v4,03/17] bpftool: Dump C through a split BTF
https://git.kernel.org/bpf/bpf-next/c/7eddda6a121b
- [bpf-next,v4,04/17] selftests/bpf: Build BTF fixtures in btf_to_tmpfile()
https://git.kernel.org/bpf/bpf-next/c/525ab88efb6d
- [bpf-next,v4,05/17] selftests/bpf: Cover unknown BTF header-extension bytes in bpftool C dumps
https://git.kernel.org/bpf/bpf-next/c/36bf1f2bde41
- [bpf-next,v4,06/17] libbpf: Let decl tags override how btf_dump renders type tags
https://git.kernel.org/bpf/bpf-next/c/fbafb695c5d2
- [bpf-next,v4,07/17] libbpf, bpftool, resolve_btfids: Dump kflagged BTF tags as is
https://git.kernel.org/bpf/bpf-next/c/79dcfd3e36a7
- [bpf-next,v4,08/17] selftests/bpf: Cover type tag rendering overrides in btf_dump
https://git.kernel.org/bpf/bpf-next/c/987293843db2
- [bpf-next,v4,09/17] selftests/bpf: Cover legacy arena type tags in bpftool C dumps
https://git.kernel.org/bpf/bpf-next/c/f857eecf674d
- [bpf-next,v4,10/17] bpftool: Apply __bpf_relocatable per record on BTF dump
https://git.kernel.org/bpf/bpf-next/c/e35e286214ba
- [bpf-next,v4,11/17] bpftool: Skip __bpf_relocatable on verifier-rewritten context types
https://git.kernel.org/bpf/bpf-next/c/8b01716790dc
- [bpf-next,v4,12/17] bpftool: Emit __bpf_static_offset on verifier-rewritten context types
https://git.kernel.org/bpf/bpf-next/c/e15918abdd48
- [bpf-next,v4,13/17] selftests/bpf: Cover record attributes in bpftool BTF dumps
https://git.kernel.org/bpf/bpf-next/c/a3335b95bd37
- [bpf-next,v4,14/17] selftests/bpf: Cover context and socket accesses through vmlinux.h
https://git.kernel.org/bpf/bpf-next/c/1fc6998042e0
- [bpf-next,v4,15/17] bpftool: Document __bpf_relocatable and __bpf_static_offset
https://git.kernel.org/bpf/bpf-next/c/aac7a06b609d
- [bpf-next,v4,16/17] bpftool: Render the arena type tag as __bpf_arena
https://git.kernel.org/bpf/bpf-next/c/40483927e5b9
- [bpf-next,v4,17/17] selftests/bpf: Cover the arena type tag in bpftool C dumps
https://git.kernel.org/bpf/bpf-next/c/325f10b127f4
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-11-06 0:30 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-05 17:58 [PATCH bpf-next v4 00/17] bpftool: Per-record CO-RE attributes in the C dump Ihor Solodrai
2026-11-05 17:58 ` [PATCH bpf-next v4 01/17] Revert "libbpf: Render the arena type tag with its address space" Ihor Solodrai
2026-11-05 17:58 ` [PATCH bpf-next v4 02/17] libbpf: Look up BTF strings without making BTF modifiable Ihor Solodrai
2026-11-05 18:41 ` bot+bpf-ci
2026-11-05 17:58 ` [PATCH bpf-next v4 03/17] bpftool: Dump C through a split BTF Ihor Solodrai
2026-11-05 17:58 ` [PATCH bpf-next v4 04/17] selftests/bpf: Build BTF fixtures in btf_to_tmpfile() Ihor Solodrai
2026-11-05 17:58 ` [PATCH bpf-next v4 05/17] selftests/bpf: Cover unknown BTF header-extension bytes in bpftool C dumps Ihor Solodrai
2026-11-05 17:58 ` [PATCH bpf-next v4 06/17] libbpf: Let decl tags override how btf_dump renders type tags Ihor Solodrai
2026-11-06 0:24 ` Andrii Nakryiko
2026-11-05 17:58 ` [PATCH bpf-next v4 07/17] libbpf, bpftool, resolve_btfids: Dump kflagged BTF tags as is Ihor Solodrai
2026-11-05 18:16 ` sashiko-bot
2026-11-06 0:25 ` Andrii Nakryiko
2026-11-05 17:58 ` [PATCH bpf-next v4 08/17] selftests/bpf: Cover type tag rendering overrides in btf_dump Ihor Solodrai
2026-11-05 17:58 ` [PATCH bpf-next v4 09/17] selftests/bpf: Cover legacy arena type tags in bpftool C dumps Ihor Solodrai
2026-11-05 17:58 ` [PATCH bpf-next v4 10/17] bpftool: Apply __bpf_relocatable per record on BTF dump Ihor Solodrai
2026-11-05 18:41 ` bot+bpf-ci
2026-11-05 17:58 ` [PATCH bpf-next v4 11/17] bpftool: Skip __bpf_relocatable on verifier-rewritten context types Ihor Solodrai
2026-11-05 17:58 ` [PATCH bpf-next v4 12/17] bpftool: Emit __bpf_static_offset " Ihor Solodrai
2026-11-05 17:58 ` [PATCH bpf-next v4 13/17] selftests/bpf: Cover record attributes in bpftool BTF dumps Ihor Solodrai
2026-11-05 17:58 ` [PATCH bpf-next v4 14/17] selftests/bpf: Cover context and socket accesses through vmlinux.h Ihor Solodrai
2026-11-05 17:58 ` [PATCH bpf-next v4 15/17] bpftool: Document __bpf_relocatable and __bpf_static_offset Ihor Solodrai
2026-11-05 17:58 ` [PATCH bpf-next v4 16/17] bpftool: Render the arena type tag as __bpf_arena Ihor Solodrai
2026-11-05 17:58 ` [PATCH bpf-next v4 17/17] selftests/bpf: Cover the arena type tag in bpftool C dumps Ihor Solodrai
2026-11-06 0:30 ` patchwork-bot+netdevbpf [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=179392500918.256564.14359701625669388609.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--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=vineet.gupta@linux.dev \
--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