From: Randy Dunlap <rdunlap@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Andrii Nakryiko <andrii@kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
bpf <bpf@vger.kernel.org>
Subject: Re: linux-next: Tree for May 12 (arch/x86/net/bpf_jit_comp32.o)
Date: Wed, 12 May 2021 11:01:35 -0700 [thread overview]
Message-ID: <08f677a5-7634-b5d2-a532-ea6d3f35200c@infradead.org> (raw)
In-Reply-To: <20210512175623.2687ac6f@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 1263 bytes --]
On 5/12/21 12:56 AM, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20210511:
>
on i386:
ld: arch/x86/net/bpf_jit_comp32.o: in function `do_jit':
bpf_jit_comp32.c:(.text+0x28c9): undefined reference to `__bpf_call_base'
ld: arch/x86/net/bpf_jit_comp32.o: in function `bpf_int_jit_compile':
bpf_jit_comp32.c:(.text+0x3694): undefined reference to `bpf_jit_blind_constants'
ld: bpf_jit_comp32.c:(.text+0x3719): undefined reference to `bpf_jit_binary_free'
ld: bpf_jit_comp32.c:(.text+0x3745): undefined reference to `bpf_jit_binary_alloc'
ld: bpf_jit_comp32.c:(.text+0x37d3): undefined reference to `bpf_jit_prog_release_other'
ld: kernel/extable.o: in function `search_exception_tables':
extable.c:(.text+0x42): undefined reference to `search_bpf_extables'
ld: kernel/extable.o: in function `kernel_text_address':
extable.c:(.text+0xee): undefined reference to `is_bpf_text_address'
ld: kernel/kallsyms.o: in function `kallsyms_lookup_size_offset':
kallsyms.c:(.text+0x254): undefined reference to `__bpf_address_lookup'
ld: kernel/kallsyms.o: in function `kallsyms_lookup_buildid':
kallsyms.c:(.text+0x2ee): undefined reference to `__bpf_address_lookup'
Full randconfig file is attached.
--
~Randy
Reported-by: Randy Dunlap <rdunlap@infradead.org>
[-- Attachment #2: config-r9260.gz --]
[-- Type: application/gzip, Size: 45092 bytes --]
next parent reply other threads:[~2021-05-12 20:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210512175623.2687ac6f@canb.auug.org.au>
2021-05-12 18:01 ` Randy Dunlap [this message]
2021-05-12 18:53 ` linux-next: Tree for May 12 (arch/x86/net/bpf_jit_comp32.o) Daniel Borkmann
2021-05-12 19:26 ` Randy Dunlap
2021-05-12 20:21 ` Daniel Borkmann
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=08f677a5-7634-b5d2-a532-ea6d3f35200c@infradead.org \
--to=rdunlap@infradead.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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;
as well as URLs for NNTP newsgroup(s).