From: Matthieu Baerts <matttbe@kernel.org>
To: Ihor Solodrai <ihor.solodrai@linux.dev>,
Eduard Zingerman <eddyz87@gmail.com>,
alan.maguire@oracle.com
Cc: bpf@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org, llvm@lists.linux.dev,
Andrii Nakryiko <andrii@kernel.org>,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Martin KaFai Lau <martin.lau@linux.dev>,
Song Liu <song@kernel.org>,
Yonghong Song <yonghong.song@linux.dev>,
John Fastabend <john.fastabend@gmail.com>,
KP Singh <kpsingh@kernel.org>,
Stanislav Fomichev <sdf@fomichev.me>, Hao Luo <haoluo@google.com>,
Jiri Olsa <jolsa@kernel.org>, Shuah Khan <shuah@kernel.org>,
Nathan Chancellor <nathan@kernel.org>,
Nick Desaulniers <nick.desaulniers+lkml@gmail.com>,
Bill Wendling <morbo@google.com>,
Justin Stitt <justinstitt@google.com>
Subject: Re: [PATCH bpf] selftests/bpf: fix implicit-function-declaration errors
Date: Sat, 4 Oct 2025 10:52:28 +0200 [thread overview]
Message-ID: <a6b7b46b-6959-458f-a975-866443351f87@kernel.org> (raw)
In-Reply-To: <c8b609ef-2d46-46b3-89ac-5ae84122cb93@linux.dev>
Hi Ihor,
On 04/10/2025 05:19, Ihor Solodrai wrote:
>
>
> On 10/3/25 8:08 PM, Ihor Solodrai wrote:
>>
>>
>> On 10/3/25 4:37 PM, Eduard Zingerman wrote:
>>> On Fri, 2025-10-03 at 17:24 +0200, Matthieu Baerts (NGI0) wrote:
>>> [...]
>>>
>>> Alan, Ihor, does this sound familiar?
>>
>> This is most likely the issue addressed in this patch:
>> https://lore.kernel.org/dwarves/f7553b3f-5827-4f50-81a9-9bd0802734b9@linux.dev/
>>
>> There wasn't a new pahole release with it yet.
>
> Not the best link, sorry. That patch wasn't picked up by lore, only
> discussion remains.
>
> Here is the commit pushed to pahole/next:
> https://git.kernel.org/pub/scm/devel/pahole/pahole.git/commit/?h=next&id=09c1e9c924da02dc02bba0a3e59490e64449df96
Thank you for the links!
OK so I guess to be (fully) able to use BTF in the future v6.18, we
should use the future Pahole v1.31, and not include extra kfuncs. Is
that correct?
If yes, we can drop this patch. (The MPTCP CI will use it internally not
to have to depend on a dev version of Pahole.)
Also, should this dependency be more explicit somehow, to help people
having errors when not using a recent enough Pahole version?
Cheers,
Matt
--
Sponsored by the NGI0 Core fund.
next prev parent reply other threads:[~2025-10-04 8:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-03 15:24 [PATCH bpf] selftests/bpf: fix implicit-function-declaration errors Matthieu Baerts (NGI0)
2025-10-03 23:37 ` Eduard Zingerman
2025-10-04 3:08 ` Ihor Solodrai
2025-10-04 3:19 ` Ihor Solodrai
2025-10-04 8:52 ` Matthieu Baerts [this message]
2025-10-04 8:51 ` Matthieu Baerts
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=a6b7b46b-6959-458f-a975-866443351f87@kernel.org \
--to=matttbe@kernel.org \
--cc=alan.maguire@oracle.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=haoluo@google.com \
--cc=ihor.solodrai@linux.dev \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=justinstitt@google.com \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=martin.lau@linux.dev \
--cc=morbo@google.com \
--cc=nathan@kernel.org \
--cc=nick.desaulniers+lkml@gmail.com \
--cc=sdf@fomichev.me \
--cc=shuah@kernel.org \
--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