BPF List
 help / color / mirror / Atom feed
From: Daniel Borkmann <daniel@iogearbox.net>
To: davem@davemloft.net
Cc: kuba@kernel.org, pabeni@redhat.com, edumazet@google.com,
	daniel@iogearbox.net, ast@kernel.org, andrii@kernel.org,
	netdev@vger.kernel.org, bpf@vger.kernel.org
Subject: pull-request: bpf 2022-07-02
Date: Sat,  2 Jul 2022 01:01:21 +0200	[thread overview]
Message-ID: <20220701230121.10354-1-daniel@iogearbox.net> (raw)

Hi David, hi Jakub, hi Paolo, hi Eric,

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

We've added 7 non-merge commits during the last 14 day(s) which contain
a total of 6 files changed, 193 insertions(+), 86 deletions(-).

The main changes are:

1) Fix clearing of page contiguity when unmapping XSK pool, from Ivan Malov.

2) Two verifier fixes around bounds data propagation, from Daniel Borkmann.

3) Fix fprobe sample module's parameter descriptions, from Masami Hiramatsu.

4) General BPF maintainer entry revamp to better scale patch reviews.

Please consider pulling these changes from:

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

Thanks a lot!

Also thanks to reporters, reviewers and testers of commits in this pull-request:

Hao Luo, Jiri Olsa, John Fastabend, KP Singh, Kuee K1r0a, Magnus 
Karlsson, Martin KaFai Lau, Mykola Lysenko, Quentin Monnet, Song Liu, 
Stanislav Fomichev, Yonghong Song

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

The following changes since commit a2b1a5d40bd12b44322c2ccd40bb0ec1699708b6:

  net/sched: sch_netem: Fix arithmetic in netem_dump() for 32-bit platforms (2022-06-17 20:29:38 -0700)

are available in the Git repository at:

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

for you to fetch changes up to a49b8ce7306cf8031361a6a4f7f6bc7a775a39c8:

  bpf, selftests: Add verifier test case for jmp32's jeq/jne (2022-07-01 12:56:27 -0700)

----------------------------------------------------------------
Alexei Starovoitov (1):
      bpf, docs: Better scale maintenance of BPF subsystem

Daniel Borkmann (4):
      bpf: Fix incorrect verifier simulation around jmp32's jeq/jne
      bpf: Fix insufficient bounds propagation from adjust_scalar_min_max_vals
      bpf, selftests: Add verifier test case for imm=0,umin=0,umax=1 scalar
      bpf, selftests: Add verifier test case for jmp32's jeq/jne

Ivan Malov (1):
      xsk: Clear page contiguity bit when unmapping pool

Masami Hiramatsu (Google) (1):
      fprobe, samples: Add module parameter descriptions

 MAINTAINERS                                  | 115 ++++++++++++++++++++++-----
 kernel/bpf/verifier.c                        | 113 +++++++++++---------------
 net/xdp/xsk_buff_pool.c                      |   1 +
 samples/fprobe/fprobe_example.c              |   7 ++
 tools/testing/selftests/bpf/verifier/jmp32.c |  21 +++++
 tools/testing/selftests/bpf/verifier/jump.c  |  22 +++++
 6 files changed, 193 insertions(+), 86 deletions(-)

             reply	other threads:[~2022-07-01 23:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-01 23:01 Daniel Borkmann [this message]
2022-07-02  3:20 ` pull-request: bpf 2022-07-02 patchwork-bot+netdevbpf

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=20220701230121.10354-1-daniel@iogearbox.net \
    --to=daniel@iogearbox.net \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    /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