From: David Miller <davem@davemloft.net>
To: daniel@iogearbox.net
Cc: ast@kernel.org, netdev@vger.kernel.org
Subject: Re: pull-request: bpf 2018-05-14
Date: Sun, 13 May 2018 21:07:21 -0400 (EDT) [thread overview]
Message-ID: <20180513.210721.1032615547496303221.davem@davemloft.net> (raw)
In-Reply-To: <20180514004710.14377-1-daniel@iogearbox.net>
From: Daniel Borkmann <daniel@iogearbox.net>
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.
prev parent reply other threads:[~2018-05-14 1:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-14 0:47 pull-request: bpf 2018-05-14 Daniel Borkmann
2018-05-14 1:07 ` David Miller [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180513.210721.1032615547496303221.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=ast@kernel.org \
--cc=daniel@iogearbox.net \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).