Received: by 10.223.176.46 with SMTP id f43csp2938448wra; Mon, 22 Jan 2018 06:01:40 -0800 (PST) X-Google-Smtp-Source: AH8x225C+UiktMN9RpQSL+9xFeWnJAxW7dW018Oo0JQXQvrluQqenQcYR1Pb5sEbbrkBfE31HfsX X-Received: by 2002:a17:902:988b:: with SMTP id s11-v6mr3503344plp.99.1516629700688; Mon, 22 Jan 2018 06:01:40 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1516629700; cv=none; d=google.com; s=arc-20160816; b=xf8VLrwjBLBhF/CKkd8GXkKwcsOVOjJBvIJ+N46QTVQnXWRAqVmQlrRTUUat6YuysX 2kXhrMMGYNJmo+nHFE0wbXlpepaqzEIKagp9JiHR+KHNlU87S0rHsboxGabN506DJRfZ ZZ/ttCwLnGzwb9muVUIQRayXJWehk72KsfgcAyL1IPTFLGap7TWUI2f7iiN30/Tn2oah sna+AZlOMfFglin+dzC4Rbw85IUu0/hlkGEASmCpotMMI4VS1a5n0OgY7M5i7Dw0LWPp F8qRJTyMufzFvoYUy+hMWrYmKiHio7ZUiwG9GjHilnoUGHetqco/JWPSwFF4ZnJkWzbZ porg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject:arc-authentication-results; bh=yxhHgtBwesfjn7Viq+QhVHidAqM2EobanN+bsBu8n+8=; b=w4kzm0IdYhDDliVliiSuuesQWnivtid1ENS384y0US00TxIUdq9qUbjC5lB2G18IDg 4aZQ12PHwPdA+460CvTuFA/h1CUPEJql2RiBdJ1CiyNClBt0NzV+Kj1xgf9FExEaKH8+ 2KW35cNtQuOiTSd4GsAwhtLIOw4Dvn6Rzyqwy0d7RL5gZDM5iVSNhClB6fUHPotwdKlC Kohp7OibylkSDUPRGZB6+iMjcxmdONsQue9ylAXiDa2T9M2BkAkLEgMuBeA3c412/WWK 4UEzDKLcRVTE4HdbJHUGDrF7kPkPjo0wbZoptuaEwbB09f4qjAu2D1zOlku4e+/UsNXg P40g== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id v70si12154201pgd.414.2018.01.22.06.01.25; Mon, 22 Jan 2018 06:01:40 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751204AbeAVOAy (ORCPT + 99 others); Mon, 22 Jan 2018 09:00:54 -0500 Received: from www62.your-server.de ([213.133.104.62]:35594 "EHLO www62.your-server.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751057AbeAVOAx (ORCPT ); Mon, 22 Jan 2018 09:00:53 -0500 Received: from [178.195.238.120] (helo=linux.home) by www62.your-server.de with esmtpsa (TLSv1.2:DHE-RSA-AES256-SHA:256) (Exim 4.85_2) (envelope-from ) id 1edceZ-00083Z-32; Mon, 22 Jan 2018 15:00:51 +0100 Subject: Re: [PATCH bpf-next 0/4] libbpf: add XDP binding support To: =?UTF-8?Q?=c3=89ric_Leblond?= Cc: Alexei Starovoitov , netdev@vger.kernel.org, linux-kernel@vger.kernel.org References: <57ad1a20-4e41-474c-8829-d6a48c6b1883@email.android.com> From: Daniel Borkmann Message-ID: <06177272-d6f1-c265-a0f8-91253c719a97@iogearbox.net> Date: Mon, 22 Jan 2018 15:00:50 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0 MIME-Version: 1.0 In-Reply-To: <57ad1a20-4e41-474c-8829-d6a48c6b1883@email.android.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit X-Authenticated-Sender: daniel@iogearbox.net X-Virus-Scanned: Clear (ClamAV 0.99.2/24245/Mon Jan 22 14:20:19 2018) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 01/20/2018 09:28 AM, Éric Leblond wrote: > Hi, > > Le 20 janv. 2018 9:21 AM, Daniel Borkmann a écrit : > > On 01/20/2018 03:27 AM, Alexei Starovoitov wrote: > > On Sat, Jan 20, 2018 at 03:00:37AM +0100, Daniel Borkmann wrote: > >> On 01/19/2018 12:43 AM, Eric Leblond wrote: > >>> Hello, > >>> > >>> This patchset rebases the libbpf code on latest bpf-next code and > addresses > >>> remarks by Daniel. > >> > >> Ok, I think it's a good start. We should later on clean up the > >> netlink handling code a bit, but that's all internal and can be > >> done in a second step. Applied to bpf-next, thanks Eric. > > > > Sorry, Eric, Daniel. > > I had to revert this patch set. It breaks build on systems > > where headers are not the most recent. > > Oops, sorry. > > > Since libbpf is used by perf it has to be built cleanly on centos7 at least. > > > > The errors I got: > > bpf.c: In function ‘bpf_set_link_xdp_fd’: > > bpf.c:456:23: error: ‘SOL_NETLINK’ undeclared (first use in this function) > > if (setsockopt(sock, SOL_NETLINK, NETLINK_EXT_ACK, > > ^~~~~~~~~~~ > > bpf.c:456:23: note: each undeclared identifier is reported only once for > each function it appears in > > bpf.c:456:36: error: ‘NETLINK_EXT_ACK’ undeclared (first use in this > function) > > if (setsockopt(sock, SOL_NETLINK, NETLINK_EXT_ACK, > > ^~~~~~~~~~~~~~~ > > nlattr.c: In function ‘nla_dump_errormsg’: > > nlattr.c:152:34: error: ‘NLMSGERR_ATTR_MAX’ undeclared (first use in this > function) > > struct nla_policy extack_policy[NLMSGERR_ATTR_MAX + 1] = { > > Yeah, fully agree, thanks for catching this, Alexei! > > What's the recommended solution here ? Include some kernel tree files or define > constant if not defined ? I think typical way is to pull such headers into tools/include/. Cheers, Daniel