From: Daniel Borkmann <daniel@iogearbox.net>
To: Randy Dunlap <rdunlap@infradead.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Linux-Next Mailing List <linux-next@vger.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
Alexei Starovoitov <ast@kernel.org>,
ppenkov@google.com, willemb@google.com
Subject: Re: linux-next: Tree for Sep 18 (kernel/bpf/syscall)
Date: Tue, 18 Sep 2018 17:41:04 +0200 [thread overview]
Message-ID: <a1129d67-97e3-8f10-c938-0de72fee9377@iogearbox.net> (raw)
In-Reply-To: <0dc91212-54e8-d2f0-a4e3-30a468c20b8d@infradead.org>
[ Cc Petar and Willem ]
On 09/18/2018 05:37 PM, Randy Dunlap wrote:
> On 9/17/18 10:12 PM, Stephen Rothwell wrote:
>> Hi all,
>>
>> Changes since 20180913:
>
> on i386 or x86_64: (in 6 of 20 randconfigs)
>
> kernel/bpf/syscall.o: In function `__x64_sys_bpf':
> syscall.c:(.text+0x3278): undefined reference to `skb_flow_dissector_bpf_prog_attach'
> syscall.c:(.text+0x3310): undefined reference to `skb_flow_dissector_bpf_prog_detach'
> kernel/bpf/syscall.o:(.rodata+0x3f0): undefined reference to `flow_dissector_prog_ops'
> kernel/bpf/verifier.o:(.rodata+0x250): undefined reference to `flow_dissector_verifier_ops'
>
> Full randconfig file is attached.
Looks like we need a wrapper for these, config had:
# CONFIG_NET is not set
next prev parent reply other threads:[~2018-09-18 15:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-18 5:12 linux-next: Tree for Sep 18 Stephen Rothwell
2018-09-18 15:37 ` linux-next: Tree for Sep 18 (kernel/bpf/syscall) Randy Dunlap
2018-09-18 15:41 ` Daniel Borkmann [this message]
2018-09-18 16:28 ` Willem de Bruijn
2018-09-18 20:22 ` Willem de Bruijn
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=a1129d67-97e3-8f10-c938-0de72fee9377@iogearbox.net \
--to=daniel@iogearbox.net \
--cc=ast@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=ppenkov@google.com \
--cc=rdunlap@infradead.org \
--cc=sfr@canb.auug.org.au \
--cc=willemb@google.com \
/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).