From: "Alexei Starovoitov" <alexei.starovoitov@gmail.com>
To: "Alan Maguire" <alan.maguire@oracle.com>, <andrii@kernel.org>,
<daniel@iogearbox.net>, <eddyz87@gmail.com>, <jolsa@kernel.org>
Cc: <ihor.solodrai@linux.dev>, <yonghong.song@linux.dev>,
<song@kernel.org>, <qmo@kernel.org>, <martin.lau@linux.dev>,
<memxor@gmail.com>, <emil@etsalapatis.com>, <mcgrof@kernel.org>,
<petr.pavlu@suse.com>, <tj@kernel.org>, <kees@kernel.org>,
<nathan@kernel.org>, <arnd@arndb.de>, <puranjay@kernel.org>,
<yatsenko@meta.com>, <atenart@kernel.org>, <ojeda@kernel.org>,
<linux-modules@vger.kernel.org>, <arnaldo.melo@gmail.com>,
<bpf@vger.kernel.org>
Subject: Re: [PATCH v4 bpf-next 6/7] selftests/bpf: Test BTF sysfs inline representations
Date: Sun, 11 Oct 2026 14:29:53 +0000 [thread overview]
Message-ID: <DM22X4LJYTQ9.1LK8R0L1FENWN@gmail.com> (raw)
In-Reply-To: <20261009112324.1442319-7-alan.maguire@oracle.com>
On Fri, Oct 09, 2026 at 12:23 PM Alan Maguire <alan.maguire@oracle.com> wrote:
> + if (stat(inline_path, &st)) {
> + err = errno;
> + if (err != ENOENT)
> + ASSERT_OK(err, "stat_inline_btf");
> + btf__free(module_btf);
> + continue;
> + }
CONFIG_DEBUG_INFO_BTF_INLINE is not in selftests/bpf/config, so in CI
every iteration ends here and btf_inline from patch 7 is skipped.
CI is green without running any of the new code.
Pls add the config.
CI builds pahole from master, so 'inline' has to be there too.
next prev parent reply other threads:[~2026-10-11 14:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-09 11:23 [PATCH v4 bpf-next 0/7] kbuild, bpf: Support inline info in BTF Alan Maguire
2026-10-09 11:23 ` [PATCH v4 bpf-next 1/7] resolve_btfids: Build separate main and inline BTF objects Alan Maguire
2026-10-09 11:23 ` [PATCH v4 bpf-next 2/7] resolve_btfids: Populate BTF link section Alan Maguire
2026-10-09 12:24 ` bot+bpf-ci
2026-10-09 11:23 ` [PATCH v4 bpf-next 3/7] kbuild, btf: Expose vmlinux inline BTF through sysfs Alan Maguire
2026-10-09 11:23 ` [PATCH v4 bpf-next 4/7] btf: Preserve string relocation maps for split BTF Alan Maguire
2026-10-09 12:01 ` sashiko-bot
2026-10-09 14:00 ` Alan Maguire
2026-10-09 11:23 ` [PATCH v4 bpf-next 5/7] btf: Relocate and expose module inline BTF Alan Maguire
2026-10-09 11:23 ` [PATCH v4 bpf-next 6/7] selftests/bpf: Test BTF sysfs inline representations Alan Maguire
2026-10-09 12:25 ` sashiko-bot
2026-10-11 14:29 ` Alexei Starovoitov [this message]
2026-10-09 11:23 ` [PATCH v4 bpf-next 7/7] selftests/bpf: Add a test verifying inline information Alan Maguire
2026-10-09 12:33 ` sashiko-bot
2026-10-11 14:40 ` [PATCH v4 bpf-next 0/7] kbuild, bpf: Support inline info in BTF patchwork-bot+netdevbpf
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=DM22X4LJYTQ9.1LK8R0L1FENWN@gmail.com \
--to=alexei.starovoitov@gmail.com \
--cc=alan.maguire@oracle.com \
--cc=andrii@kernel.org \
--cc=arnaldo.melo@gmail.com \
--cc=arnd@arndb.de \
--cc=atenart@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=kees@kernel.org \
--cc=linux-modules@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=mcgrof@kernel.org \
--cc=memxor@gmail.com \
--cc=nathan@kernel.org \
--cc=ojeda@kernel.org \
--cc=petr.pavlu@suse.com \
--cc=puranjay@kernel.org \
--cc=qmo@kernel.org \
--cc=song@kernel.org \
--cc=tj@kernel.org \
--cc=yatsenko@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