netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Borkmann <daniel@iogearbox.net>
To: davem@davemloft.net
Cc: daniel@iogearbox.net, ast@kernel.org, netdev@vger.kernel.org
Subject: pull-request: bpf 2019-01-11
Date: Fri, 11 Jan 2019 11:00:01 +0100	[thread overview]
Message-ID: <20190111100001.310-1-daniel@iogearbox.net> (raw)

Hi David,

The following pull-request contains BPF updates for your *net* tree.

The main changes are:

1) Fix TCP-BPF support for correctly setting the initial window
   via TCP_BPF_IW on an active TFO sender, from Yuchung.

2) Fix a panic in BPF's stack_map_get_build_id()'s ELF parsing on
   32 bit archs caused by page_address() returning NULL, from Song.

3) Fix BTF pretty print in kernel and bpftool when bitfield member
   offset is greater than 256. Also add test cases, from Yonghong.

4) Fix improper argument handling in xdp1 sample, from Ioana.

5) Install missing tcp_server.py and tcp_client.py files from
   BPF selftests, from Anders.

6) Add test_libbpf to gitignore in libbpf and BPF selftests,
   from Stanislav.

Please consider pulling these changes from:

  git://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf.git

Thanks a lot!

----------------------------------------------------------------

The following changes since commit d972f3dce8d161e2142da0ab1ef25df00e2f21a9:

  packet: Do not leak dev refcounts on error exit (2019-01-08 21:41:40 -0500)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf.git 

for you to fetch changes up to fb4129b9279dc40be51060004e8f5e4b360739b8:

  Merge branch 'bpf-fix-bitfield-printing' (2019-01-11 10:40:56 +0100)

----------------------------------------------------------------
Anders Roxell (1):
      selftests: bpf: install files tcp_(server|client)*.py

Daniel Borkmann (1):
      Merge branch 'bpf-fix-bitfield-printing'

Ioana Ciornei (1):
      samples: bpf: user proper argument index

Song Liu (1):
      bpf: fix panic in stack_map_get_build_id() on i386 and arm32

Stanislav Fomichev (1):
      selftests/bpf: add missing executables to .gitignore

Yonghong Song (3):
      bpf: fix bpffs bitfield pretty print
      tools/bpf: test btf bitfield with >=256 struct member offset
      tools/bpf: fix bpftool map dump with bitfields

Yuchung Cheng (1):
      bpf: correctly set initial window on active Fast Open sender

 kernel/bpf/btf.c                       | 12 ++++++------
 kernel/bpf/stackmap.c                  |  3 ++-
 net/core/filter.c                      |  2 +-
 samples/bpf/xdp1_user.c                |  2 +-
 tools/bpf/bpftool/btf_dumper.c         | 13 +++++++------
 tools/lib/bpf/.gitignore               |  1 +
 tools/testing/selftests/bpf/.gitignore |  1 +
 tools/testing/selftests/bpf/Makefile   |  4 +++-
 tools/testing/selftests/bpf/test_btf.c | 29 +++++++++++++++++++++--------
 9 files changed, 43 insertions(+), 24 deletions(-)

             reply	other threads:[~2019-01-11 10:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-11 10:00 Daniel Borkmann [this message]
2019-01-11 20:52 ` pull-request: bpf 2019-01-11 David Miller

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=20190111100001.310-1-daniel@iogearbox.net \
    --to=daniel@iogearbox.net \
    --cc=ast@kernel.org \
    --cc=davem@davemloft.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).