From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.9 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 2C0EDC2D0CF for ; Tue, 24 Dec 2019 15:49:24 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id F303B20643 for ; Tue, 24 Dec 2019 15:49:23 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=redhat.com header.i=@redhat.com header.b="Lov7OXwO" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726861AbfLXPtX (ORCPT ); Tue, 24 Dec 2019 10:49:23 -0500 Received: from us-smtp-delivery-1.mimecast.com ([205.139.110.120]:53513 "EHLO us-smtp-1.mimecast.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1726853AbfLXPtX (ORCPT ); Tue, 24 Dec 2019 10:49:23 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1577202562; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=Ym5Rj89pLJN6P8a7v9msWZpoU2JaL1iBGr+uuDCwvGg=; b=Lov7OXwOT2DwQrjbER+aa6Hf3x0APdDkgc4w9mQ+9SCondNkIFxzCErpqeMhHge+w5JU3y jbFXSvumt0eYNJj9Zjrp2xp56oGVeDKSlAP7ymJlrNca/isULKj0yhA09TdShiTrqOBTC/ BNC24vFSfYavdv448gD7nvSF8VJe/70= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-246-V2JwHFw5O1a2P9AM01dlsQ-1; Tue, 24 Dec 2019 10:49:18 -0500 X-MC-Unique: V2JwHFw5O1a2P9AM01dlsQ-1 Received: from smtp.corp.redhat.com (int-mx07.intmail.prod.int.phx2.redhat.com [10.5.11.22]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 5FB081005502; Tue, 24 Dec 2019 15:49:17 +0000 (UTC) Received: from [10.36.116.145] (ovpn-116-145.ams2.redhat.com [10.36.116.145]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 46C2E1036D00; Tue, 24 Dec 2019 15:49:16 +0000 (UTC) From: "Eelco Chaudron" To: "Andrii Nakryiko" Cc: bpf , "David S. Miller" , "Alexei Starovoitov" , Networking Subject: Re: [PATCH bpf-next] selftests/bpf: Add a test for attaching a bpf fentry/fexit trace to an XDP program Date: Tue, 24 Dec 2019 16:49:14 +0100 Message-ID: In-Reply-To: References: <157675340354.60799.13351496736033615965.stgit@xdp-tutorial> MIME-Version: 1.0 Content-Type: text/plain X-Scanned-By: MIMEDefang 2.84 on 10.5.11.22 Sender: bpf-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: bpf@vger.kernel.org On 23 Dec 2019, at 18:57, Andrii Nakryiko wrote: > On Mon, Dec 23, 2019 at 4:54 AM Eelco Chaudron wrote: > >> Thanks for the review, updated my kernel to the latest bfp-next, but now >> I get the following build issue for the test suite: >> >> GEN-SKEL [test_progs] loop3.skel.h >> GEN-SKEL [test_progs] test_skeleton.skel.h >> libbpf: failed to find BTF for extern 'CONFIG_BPF_SYSCALL': -2 > > This looks like you have Clang without BTF types for extern. Can you > try pull the very latest Clang/LLVM and try again? The latest commit > you should have is e3d8ee35e4ad ("reland "[DebugInfo] Support to emit > debugInfo for extern variables""). > Thanks, rebuilding the latest master LLVM fixed the problem! //Eelco