Received: by 10.223.176.46 with SMTP id f43csp575871wra; Sat, 20 Jan 2018 00:22:59 -0800 (PST) X-Google-Smtp-Source: AH8x22501Y+51eUrfs+QJD5QLoyqX4w4QvkZyA1sJHtgYRcshfJvu6SjeIrLapJGNqTsO18cq2PP X-Received: by 10.98.63.93 with SMTP id m90mr1468925pfa.231.1516436579407; Sat, 20 Jan 2018 00:22:59 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1516436579; cv=none; d=google.com; s=arc-20160816; b=OxjAdvv8lkWl4tdA7shtPPhXeHUA/27sNyx2dumi6lMUQVFXwha0Jg45s9JgAh9N5Q RLbvpX7IqksLbpTtQbI3PReJ2gJXKb8HCz15MqqwHMehNS+YEwxF2zjLg8Uh6sPQlV9r 5mPgckk4Ij0ktEstklj0StltTSE5Y0g7Y5ldgmeuQqEBkRAzsNfEFv4kAfo+zaChQ9ZI na6n9N9BBDfAPnk6oX5MJNl8djYIBUJaC8MDVXiuMWnWatz+3r2Rc4flHMhHFeYx3Q44 /HY+yMhcgoMeWwNn2+wzYNAzLKlxTqqIAvIqSs72YFjoCBTfCnDJ8/wiBn5wSP3KwVRx K29g== 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=ZXzd/DdvO6TD6HKJ76b7DVlFbORo8DBgugklMBGYJMI=; b=afNEWWB4Co1bhjq2nfh21YvUF3SqzIvgVR+59L4YQqmCN55ploKTHWEMbldbfbK6Nu EOkwyTYCUV8FZRQXLKYM/GmiC0sk3KGf/ZlBd9G2ZaeCrjd35d/L8yUwBdcXviltOytP JCt+KOakUbX1WnbpGLYgl0l5h7IFEa2EilY19Mx10z6/YVIqTVmuPGXk0n8yQSMcOnJj QD7fAsDimU9W6lxkm2dFOCGYMbSQ5XeOYVcls+UrcoxCOu1Cs8K8lWfJOPkqxNfHAddv WQ/cQFqViiogdsjozfp6PT5e9rM7mijBTxO+INCWlgAvORYhuRMwX3sF4n5kzfLS1DqM X24g== 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 u26si5957960pge.210.2018.01.20.00.22.45; Sat, 20 Jan 2018 00:22:59 -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 S1754710AbeATIVV (ORCPT + 99 others); Sat, 20 Jan 2018 03:21:21 -0500 Received: from www62.your-server.de ([213.133.104.62]:38335 "EHLO www62.your-server.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751055AbeATIVM (ORCPT ); Sat, 20 Jan 2018 03:21:12 -0500 Received: from [62.202.221.5] (helo=linux.home) by www62.your-server.de with esmtpsa (TLSv1.2:DHE-RSA-AES256-SHA:256) (Exim 4.85_2) (envelope-from ) id 1ecoOk-0000ez-GT; Sat, 20 Jan 2018 09:21:10 +0100 Subject: Re: [PATCH bpf-next 0/4] libbpf: add XDP binding support To: Alexei Starovoitov Cc: Eric Leblond , netdev@vger.kernel.org, linux-kernel@vger.kernel.org References: <1516318537.24936.7.camel@regit.org> <20180118234332.28996-1-eric@regit.org> <2a008274-a09d-71ed-4c1e-5d7aa2bb8797@iogearbox.net> <20180120022753.psuzgzmxqaubh5t3@ast-mbp> From: Daniel Borkmann Message-ID: <4dc597a1-5046-3805-eb81-03a23bf0acbb@iogearbox.net> Date: Sat, 20 Jan 2018 09:21:10 +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: <20180120022753.psuzgzmxqaubh5t3@ast-mbp> 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/24238/Sat Jan 20 06:20:02 2018) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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. > > 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!