From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752262AbdLMBct (ORCPT ); Tue, 12 Dec 2017 20:32:49 -0500 Received: from ozlabs.org ([103.22.144.67]:59983 "EHLO ozlabs.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750749AbdLMBcr (ORCPT ); Tue, 12 Dec 2017 20:32:47 -0500 Date: Wed, 13 Dec 2017 12:32:45 +1100 From: Stephen Rothwell To: Daniel Borkmann , Alexei Starovoitov , Networking Cc: Linux-Next Mailing List , Linux Kernel Mailing List , Yonghong Song Subject: linux-next: build failure after merge of the bpf-next tree Message-ID: <20171213123245.44c86f3f@canb.auug.org.au> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi all, After merging the bpf-next tree, today's linux-next build (arm multi_v7_defconfig) failed like this: kernel/events/core.o: In function `perf_ioctl': core.c:(.text+0x98c4): undefined reference to `bpf_event_query_prog_array' Caused by commit f371b304f12e ("bpf/tracing: allow user space to query prog array on the same tp") CONFIG_BPF_SYSCALL is not set for this build. I have used the bpf-next tree from next-20171212 for today. -- Cheers, Stephen Rothwell