From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Miller Subject: Re: pull-request: bpf 2018-05-14 Date: Sun, 13 May 2018 21:07:21 -0400 (EDT) Message-ID: <20180513.210721.1032615547496303221.davem@davemloft.net> References: <20180514004710.14377-1-daniel@iogearbox.net> Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: ast@kernel.org, netdev@vger.kernel.org To: daniel@iogearbox.net Return-path: Received: from shards.monkeyblade.net ([184.105.139.130]:51840 "EHLO shards.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751338AbeENBHW (ORCPT ); Sun, 13 May 2018 21:07:22 -0400 In-Reply-To: <20180514004710.14377-1-daniel@iogearbox.net> Sender: netdev-owner@vger.kernel.org List-ID: From: Daniel Borkmann Date: Mon, 14 May 2018 02:47:10 +0200 > The following pull-request contains BPF updates for your *net* tree. > > The main changes are: > > 1) Fix nfp to allow zero-length BPF capabilities, meaning the nfp > capability parsing loop will otherwise exit early if the last > capability is zero length and therefore driver will fail to probe > with an error such as: > > nfp: BPF capabilities left after parsing, parsed:92 total length:100 > nfp: invalid BPF capabilities at offset:92 > > Fix from Jakub. > > 2) libbpf's bpf_object__open() may return IS_ERR_OR_NULL() and not > just an error. Fix libbpf's bpf_prog_load_xattr() to handle that > case as well, also from Jakub. > > Please consider pulling these changes from: > > git://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf.git Pulled, thanks Daniel.