BPF List
 help / color / mirror / Atom feed
From: Eduard Zingerman <eddyz87@gmail.com>
To: Mykola Lysenko <nickolay.lysenko@gmail.com>, bpf@vger.kernel.org
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
	martin.lau@linux.dev, 	song@kernel.org, yonghong.song@linux.dev,
	jolsa@kernel.org, memxor@gmail.com
Subject: Re: [PATCH bpf-next v7 2/9] selftests/bpf: drop stale lines, restore two header dependencies
Date: Mon, 24 Aug 2026 15:47:10 -0700	[thread overview]
Message-ID: <08a3b5f472899c06ff43f0b8e71c6f9c4871143a.camel@gmail.com> (raw)
In-Reply-To: <20260823194241.3415152-3-nickolay.lysenko@gmail.com>

On Sun, 2026-08-23 at 12:42 -0700, Mykola Lysenko wrote:
> Four target-specific lines name objects nothing builds. Three name
> the BPF objects by their pre-rename names: commit afef88e65554
> ("selftests/bpf: Store BPF object files with .bpf.o extension") left
> them without a target; the flow_dissector_load.o dependency names an
> intermediate the generic one-step compile+link rule does not produce.
> 
> Three linked-skeleton dependency map entries (xsk_xdp_progs,
> xdp_hw_metadata, xdp_features) were dead on arrival: commit
> f0a249df1b07 ("selftests/xsk: get rid of built-in XDP program"),
> commit 297a3f124155 ("selftests/bpf: Simple program to dump XDP RX
> metadata") and commit 4dba3e7852b7 ("selftests/bpf: introduce XDP
> compliance test tool") each added one, mimicking the neighboring
> entries without adding the skeleton to LINKED_SKELS, the only place
> the -deps map is read from; these three skeletons are generated by
> the regular pattern rule, which never consults it.
> 
> The '-fno-inline' pair (test_l4lb_noinline, test_xdp_noinline) had
> stopped taking effect even earlier, with commit 74b5a5968fe8
> ("selftests/bpf: Replace test_progs and test_maps w/ general rule"):
> since then the BPF compile recipe expands TRUNNER_BPF_CFLAGS, a
> simply-expanded copy of BPF_CFLAGS taken when the runner rules are
> instantiated, which a target-specific 'BPF_CFLAGS +=' cannot reach.
> Both programs have compiled without the flag since, and nothing was
> lost: every function they define
> carries a noinline annotation, except the SEC() entry points, which
> nothing in the file calls, and the single __always_inline helper in
> each, a deliberate exception the flag never overrode; and
> compiling with -fno-inline restored yields byte-identical objects.
> 
> The two header dependencies with remaining value are restored in
> working form. flow_dissector_load.h moves to the binary itself, which
> is linked straight from its .c by the generic '$(OUTPUT)/%:%.c' rule
> - editing the header now rebuilds it - on the line that already lists
> the binary's helper object. cgroup_getset_retval_hooks.h -
> added by commit e7215f574079 ("selftests/bpf: Make sure
> bpf_{g,s}et_retval is exposed everywhere") days before the rename
> orphaned it - lived in the top directory, outside the progs/*.h
> blanket prerequisite of the BPF object rules, so editing it never
> rebuilt the BPF object. Move it under progs/, next to its only BPF
> consumer, where the blanket prerequisite covers it - the arrangement
> several other headers shared between progs/ and prog_tests/ already
> use. Its userspace consumer is tracked exactly by the
> compiler-generated dependency files.
> 
> 'CURDIR := $(abspath .)' redefines make's builtin to the value it
> already has, and 'OBJCOPY ?= $(CROSS_COMPILE)objcopy' defines a
> variable nothing in the selftests build or the included kselftest
> infrastructure ever reads; drop both.
> 
> Signed-off-by: Mykola Lysenko <nickolay.lysenko@gmail.com>
> ---

Acked-by: Eduard Zingerman <eddyz87@gmail.com>

...

  parent reply	other threads:[~2026-08-24 22:47 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-23 19:42 [PATCH bpf-next v7 0/9] selftests/bpf: restructure the Makefile as a layered build Mykola Lysenko
2026-08-23 19:42 ` [PATCH bpf-next v7 1/9] selftests/bpf: keep headers off the generic link command line Mykola Lysenko
2026-08-23 19:42 ` [PATCH bpf-next v7 2/9] selftests/bpf: drop stale lines, restore two header dependencies Mykola Lysenko
2026-08-23 20:41   ` bot+bpf-ci
2026-08-24 22:47   ` Eduard Zingerman [this message]
2026-08-23 19:42 ` [PATCH bpf-next v7 3/9] selftests/bpf: factor the permissive-mode skip suffix into a helper Mykola Lysenko
2026-08-23 19:51   ` sashiko-bot
2026-08-23 19:42 ` [PATCH bpf-next v7 4/9] selftests/bpf: generate the signing key and certificate once Mykola Lysenko
2026-08-23 19:42 ` [PATCH bpf-next v7 5/9] selftests/bpf: generate verifier/tests.h in a regular recipe Mykola Lysenko
2026-08-23 19:42 ` [PATCH bpf-next v7 6/9] selftests/bpf: derive the bench object list from the sources Mykola Lysenko
2026-08-24 23:42   ` Eduard Zingerman
2026-08-23 19:42 ` [PATCH bpf-next v7 7/9] selftests/bpf: extract BPF skeleton generation into a helper script Mykola Lysenko
2026-08-23 19:42 ` [PATCH bpf-next v7 8/9] selftests/bpf: move shared build definitions into Makefile.buildvars Mykola Lysenko
2026-08-23 20:53   ` bot+bpf-ci
2026-08-25  6:45   ` Eduard Zingerman
2026-08-23 19:42 ` [PATCH bpf-next v7 9/9] selftests/bpf: build each test runner instance in its own sub-make Mykola Lysenko
2026-08-23 21:05   ` bot+bpf-ci
2026-08-25 23:55   ` Eduard Zingerman
2026-08-26  4:58     ` Eduard Zingerman

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=08a3b5f472899c06ff43f0b8e71c6f9c4871143a.camel@gmail.com \
    --to=eddyz87@gmail.com \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=jolsa@kernel.org \
    --cc=martin.lau@linux.dev \
    --cc=memxor@gmail.com \
    --cc=nickolay.lysenko@gmail.com \
    --cc=song@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