mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: bot+bpf-ci@kernel.org
To: tweek@google.com,qmo@kernel.org,ast@kernel.org,daniel@iogearbox.net,andrii@kernel.org,eddyz87@gmail.com,memxor@gmail.com,shuah@kernel.org,tweek@google.com,kpsingh@kernel.org,leon.hwang@linux.dev,emil@etsalapatis.com
Cc: martin.lau@linux.dev,song@kernel.org,yonghong.song@linux.dev,jolsa@kernel.org,ihor.solodrai@linux.dev,bpf@vger.kernel.org,linux-kernel@vger.kernel.org,linux-kselftest@vger.kernel.org,ast@kernel.org,andrii@kernel.org,daniel@iogearbox.net,martin.lau@kernel.org,eddyz87@gmail.com,yonghong.song@linux.dev,mason@kernel.org,ihor.solodrai@linux.dev
Subject: Re: [PATCH bpf-next 1/2] bpftool: Skip non-autoload programs when generating light skeletons
Date: Tue,  8 Sep 2026 16:01:49 +0000 (UTC)	[thread overview]
Message-ID: <70e2a2f4354a7eb6208944e1ab2c13dadcb8b78cdbe2888ad4471124b1cc81b7@mail.kernel.org> (raw)
In-Reply-To: <20260908065529.901593-1-tweek@google.com>

[-- Attachment #1: Type: text/plain, Size: 3563 bytes --]

> diff --git a/tools/bpf/bpftool/Documentation/bpftool-gen.rst b/tools/bpf/bpftool/Documentation/bpftool-gen.rst
> index d0a36f442db7..1cdecf3e4fa5 100644
> --- a/tools/bpf/bpftool/Documentation/bpftool-gen.rst
> +++ b/tools/bpf/bpftool/Documentation/bpftool-gen.rst

[ ... ]

> diff --git a/tools/bpf/bpftool/gen.c b/tools/bpf/bpftool/gen.c
> index a50540ef6521..0fcfe20ff515 100644
> --- a/tools/bpf/bpftool/gen.c
> +++ b/tools/bpf/bpftool/gen.c
> @@ -583,6 +583,9 @@ static void codegen_attach_detach(struct bpf_object *obj, const char *obj_name)
>  	bpf_object__for_each_program(prog, obj) {
>  		const char *tp_name;
>
> +		if (!bpf_program__autoload(prog))
> +			continue;
> +
>  		codegen("\
>  			\n\
>  			\n\

[ ... ]

> @@ -1339,6 +1348,8 @@ static int do_skeleton(int argc, char **argv)
>  		map_cnt++;
>  	}
>  	bpf_object__for_each_program(prog, obj) {
> +		if (use_loader && !bpf_program__autoload(prog))
> +			continue;
>  		prog_cnt++;
>  	}

Can the autoload flag change between when this check runs and when
codegen_attach_detach() checks it?

Looking at the code flow, do_skeleton() samples bpf_program__autoload() here
before calling bpf_object__load(), but codegen_attach_detach() and
codegen_destroy() (which also check autoload at gen.c:586, 635, 654, and 686)
run inside gen_trace() after bpf_object__load() completes.

In tools/lib/bpf/libbpf.c, bpf_object__load() ->
bpf_object_prepare() modifies prog->autoload for struct_ops programs:

1. bpf_object__init_kern_struct_ops_maps() (libbpf.c:1251, 1290) sets
   st_ops->progs[i]->autoload = false when the member is missing from kernel
   BTF or the slot was replaced/NULLed.

2. bpf_object_adjust_struct_ops_autoload() (libbpf.c:1166) sets
   prog->autoload = should_load for programs referenced by struct_ops maps,
   which can flip SEC("?struct_ops/...") programs from false back to true when
   the referencing map has autocreate set.

For the false->true case (SEC("?struct_ops/foo") with an autocreated map):
do_skeleton() omits both the progs and links struct fields, but
codegen_attach_detach()/codegen_destroy() then emit attach functions
referencing skel->progs.foo.prog_fd and skel->links.foo_fd, which weren't
declared.

For the true->false case (plain SEC("struct_ops/foo") whose member is missing
from kernel BTF): the fields are emitted but attach/detach/destroy skip the
program, and the loader doesn't reserve a prog_fd slot for it, so subsequent
program FDs get written into preceding fields.

Would it work to sample autoload once and reuse that decision, or to move the
struct field emission after bpf_object__load()?

> @@ -1402,6 +1413,8 @@ static int do_skeleton(int argc, char **argv)
>  	if (prog_cnt) {
>  		printf("\tstruct {\n");
>  		bpf_object__for_each_program(prog, obj) {
> +			if (use_loader && !bpf_program__autoload(prog))
> +				continue;
>  			if (use_loader)
>  				printf("\t\tstruct bpf_prog_desc %s;\n",
>  				       bpf_program__name(prog));

[ ... ]

> @@ -1415,6 +1428,8 @@ static int do_skeleton(int argc, char **argv)
>  	if (prog_cnt + attach_map_cnt) {
>  		printf("\tstruct {\n");
>  		bpf_object__for_each_program(prog, obj) {
> +			if (use_loader && !bpf_program__autoload(prog))
> +				continue;
>  			if (use_loader)
>  				printf("\t\tint %s_fd;\n",
>  				       bpf_program__name(prog));


---
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/34245369055

  parent reply	other threads:[~2026-09-08 16:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-08  6:55 Thiébaud Weksteen
2026-09-08  6:55 ` [PATCH bpf-next 2/2] selftests/bpf: Verify program FD after non-autoload programs in lskel Thiébaud Weksteen
2026-09-08 15:46   ` bot+bpf-ci
2026-09-08 16:01 ` bot+bpf-ci [this message]
2026-09-08 23:48   ` [PATCH bpf-next 1/2] bpftool: Skip non-autoload programs when generating light skeletons Quentin Monnet

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=70e2a2f4354a7eb6208944e1ab2c13dadcb8b78cdbe2888ad4471124b1cc81b7@mail.kernel.org \
    --to=bot+bpf-ci@kernel.org \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=eddyz87@gmail.com \
    --cc=emil@etsalapatis.com \
    --cc=ihor.solodrai@linux.dev \
    --cc=jolsa@kernel.org \
    --cc=kpsingh@kernel.org \
    --cc=leon.hwang@linux.dev \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=martin.lau@kernel.org \
    --cc=martin.lau@linux.dev \
    --cc=mason@kernel.org \
    --cc=memxor@gmail.com \
    --cc=qmo@kernel.org \
    --cc=shuah@kernel.org \
    --cc=song@kernel.org \
    --cc=tweek@google.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

all inboxes | Powered by JetHome®