From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Daniel Xu <dxu@dxuuu.xyz>
Cc: Daniel Borkmann <daniel@iogearbox.net>,
Alexei Starovoitov <ast@kernel.org>,
Andrii Nakryiko <andrii@kernel.org>, bpf <bpf@vger.kernel.org>,
Networking <netdev@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: runtime warnings after merge of the bpf-next tree
Date: Thu, 1 Feb 2024 15:53:39 +1100 [thread overview]
Message-ID: <20240201155339.2b5936be@canb.auug.org.au> (raw)
In-Reply-To: <yeujnwul3nd6vhk2pidnh72l5lx4zp4sgup4qzgbe2fpex42yf@2wtt67dvl7s3>
[-- Attachment #1: Type: text/plain, Size: 1251 bytes --]
Hi Daniel,
On Wed, 31 Jan 2024 20:55:43 -0700 Daniel Xu <dxu@dxuuu.xyz> wrote:
>
> Hi Stephen,
>
> Thanks for the report.
>
> On Thu, Feb 01, 2024 at 02:23:48PM +1100, Stephen Rothwell wrote:
> > Hi all,
> >
> > After merging the bpf-next tree, today's linux-next build (powerpc
> > pseries_le_defconfig) produced these runtime warnings in my qemu boot
>
> I can't quite find that config in-tree. Mind giving me a pointer?
Its a constructed config ("make pseries_le_config")
$ grep BPF .config
CONFIG_BPF=y
CONFIG_HAVE_EBPF_JIT=y
CONFIG_ARCH_WANT_DEFAULT_BPF_JIT=y
# BPF subsystem
CONFIG_BPF_SYSCALL=y
CONFIG_BPF_JIT=y
# CONFIG_BPF_JIT_ALWAYS_ON is not set
CONFIG_BPF_JIT_DEFAULT_ON=y
CONFIG_BPF_UNPRIV_DEFAULT_OFF=y
# CONFIG_BPF_PRELOAD is not set
CONFIG_BPF_LSM=y
# end of BPF subsystem
CONFIG_CGROUP_BPF=y
CONFIG_NETFILTER_BPF_LINK=y
CONFIG_NET_CLS_BPF=m
CONFIG_NET_ACT_BPF=m
# CONFIG_BPF_STREAM_PARSER is not set
# HID-BPF support
# end of HID-BPF support
CONFIG_BPF_EVENTS=y
CONFIG_TEST_BPF=m
> My guess is the config does not enable CONFIG_DEBUG_INFO_BTF which
> causes compilation to use the dummy definitions for BTF_KFUNCS_START().
Correct, see above.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2024-02-01 4:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-01 3:23 linux-next: runtime warnings after merge of the bpf-next tree Stephen Rothwell
2024-02-01 3:55 ` Alexei Starovoitov
2024-02-01 4:47 ` Stephen Rothwell
2024-02-01 3:55 ` Daniel Xu
2024-02-01 4:02 ` Alexei Starovoitov
2024-02-01 5:31 ` Stephen Rothwell
2024-02-01 4:53 ` Stephen Rothwell [this message]
2024-02-01 11:31 ` Marek Szyprowski
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=20240201155339.2b5936be@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=dxu@dxuuu.xyz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/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