From: David Miller <davem@davemloft.net>
To: daniel@iogearbox.net
Cc: ast@kernel.org, netdev@vger.kernel.org
Subject: Re: pull-request: bpf-next 2018-03-03
Date: Fri, 02 Mar 2018 21:53:32 -0500 (EST) [thread overview]
Message-ID: <20180302.215332.1486001602115971517.davem@davemloft.net> (raw)
In-Reply-To: <20180303014201.28208-1-daniel@iogearbox.net>
From: Daniel Borkmann <daniel@iogearbox.net>
Date: Sat, 3 Mar 2018 02:42:01 +0100
> The following pull-request contains BPF updates for your *net-next* tree.
>
> The main changes are:
>
> 1) Extend bpftool to build up CFG information of eBPF programs and add an
> option to dump this in DOT format such that this can later be used with
> DOT graphic tools (xdot, graphviz, etc) to visualize it. Part of the
> analysis performed is sub-program detection and basic-block partitioning,
> from Jiong.
>
> 2) Multiple enhancements for bpftool's batch mode, more specifically the
> parser now understands comments (#), continuation lines (\), and arguments
> enclosed between quotes. Also, allow to read from stdin via '-' as input
> file, all from Quentin.
>
> 3) Improve BPF kselftests by i) unifying the rlimit handling into a helper
> that is then used by all tests, and ii) add support for testing tail calls
> to test_verifier plus add tests covering all corner cases. The latter is
> especially useful for testing JITs, from Daniel.
>
> 4) Remove x64 JIT's bpf_flush_icache() since flush_icache_range() is a noop
> on x64, from Daniel.
>
> 5) Fix one more occasion in BPF samples where we do not detach the BPF program
> from the cgroup after completion, from Prashant.
>
> Please consider pulling these changes from:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next.git
Pulled, thanks Daniel.
prev parent reply other threads:[~2018-03-03 2:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-03 1:42 pull-request: bpf-next 2018-03-03 Daniel Borkmann
2018-03-03 2:53 ` 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=20180302.215332.1486001602115971517.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).