All of lore.kernel.org
 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,
	martin.lau@linux.dev, netdev@vger.kernel.org,
	bpf@vger.kernel.org
Subject: pull-request: bpf 2023-03-23
Date: Thu, 23 Mar 2023 23:52:21 +0100	[thread overview]
Message-ID: <20230323225221.6082-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 8 non-merge commits during the last 13 day(s) which contain
a total of 21 files changed, 238 insertions(+), 161 deletions(-).

The main changes are:

1) Fix verification issues in some BPF programs due to their stack usage
   patterns, from Eduard Zingerman.

2) Fix to add missing overflow checks in xdp_umem_reg and return an error
   in such case, from Kal Conley.

3) Fix and undo poisoning of strlcpy in libbpf given it broke builds for
   libcs which provided the former like uClibc-ng, from Jesus Sanchez-Palencia.

4) Fix insufficient bpf_jit_limit default to avoid users running into hard
   to debug seccomp BPF errors, from Daniel Borkmann.

5) Fix driver return code when they don't support a bpf_xdp_metadata kfunc
   to make it unambiguous from other errors, from Jesper Dangaard Brouer.

6) Two BPF selftest fixes to address compilation errors from recent changes
   in kernel structures, from Alexei Starovoitov.

Please consider pulling these changes from:

  git://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf.git tags/for-netdev

Thanks a lot!

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

Andrii Nakryiko, Kuniyuki Iwashima, Lefteris Alexakis, Magnus Karlsson, 
Stanislav Fomichev, Stephen Haynes, Tariq Toukan, Toke Høiland-Jørgensen

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

The following changes since commit bced3f7db95ff2e6ca29dc4d1c9751ab5e736a09:

  tcp: tcp_make_synack() can be called from process context (2023-03-09 23:12:00 -0800)

are available in the Git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf.git tags/for-netdev

for you to fetch changes up to 915efd8a446b74442039d31689d5d863caf82517:

  xdp: bpf_xdp_metadata use EOPNOTSUPP for no driver support (2023-03-22 09:11:09 -0700)

----------------------------------------------------------------
bpf-for-netdev

----------------------------------------------------------------
Alexei Starovoitov (4):
      Merge branch 'bpf: Allow reads from uninit stack'
      selftests/bpf: Fix progs/find_vma_fail1.c build error.
      selftests/bpf: Fix progs/test_deny_namespace.c issues.
      Merge branch 'bpf: Allow reads from uninit stack'

Daniel Borkmann (1):
      bpf: Adjust insufficient default bpf_jit_limit

Eduard Zingerman (2):
      bpf: Allow reads from uninit stack
      selftests/bpf: Tests for uninitialized stack reads

Jesper Dangaard Brouer (1):
      xdp: bpf_xdp_metadata use EOPNOTSUPP for no driver support

Jesus Sanchez-Palencia (1):
      libbpf: Revert poisoning of strlcpy

Kal Conley (1):
      xsk: Add missing overflow check in xdp_umem_reg

 Documentation/networking/xdp-rx-metadata.rst       |   7 +-
 drivers/net/ethernet/mellanox/mlx4/en_rx.c         |   4 +-
 drivers/net/ethernet/mellanox/mlx5/core/en/xdp.c   |   4 +-
 drivers/net/veth.c                                 |   4 +-
 kernel/bpf/core.c                                  |   2 +-
 kernel/bpf/verifier.c                              |  11 ++-
 net/core/xdp.c                                     |  10 +-
 net/xdp/xdp_umem.c                                 |  13 +--
 tools/lib/bpf/libbpf_internal.h                    |   4 +-
 .../selftests/bpf/prog_tests/uninit_stack.c        |   9 ++
 tools/testing/selftests/bpf/progs/find_vma_fail1.c |   1 +
 .../selftests/bpf/progs/test_deny_namespace.c      |  10 +-
 .../selftests/bpf/progs/test_global_func10.c       |   8 +-
 tools/testing/selftests/bpf/progs/uninit_stack.c   |  87 +++++++++++++++++
 tools/testing/selftests/bpf/verifier/calls.c       |  13 ++-
 .../selftests/bpf/verifier/helper_access_var_len.c | 104 ++++++++++++++-------
 tools/testing/selftests/bpf/verifier/int_ptr.c     |   9 +-
 .../selftests/bpf/verifier/search_pruning.c        |  13 ++-
 tools/testing/selftests/bpf/verifier/sock.c        |  27 ------
 tools/testing/selftests/bpf/verifier/spill_fill.c  |   7 +-
 tools/testing/selftests/bpf/verifier/var_off.c     |  52 -----------
 21 files changed, 238 insertions(+), 161 deletions(-)
 create mode 100644 tools/testing/selftests/bpf/prog_tests/uninit_stack.c
 create mode 100644 tools/testing/selftests/bpf/progs/uninit_stack.c

             reply	other threads:[~2023-03-23 22:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-23 22:52 Daniel Borkmann [this message]
2023-03-23 23:36 ` pull-request: bpf 2023-03-23 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=20230323225221.6082-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=martin.lau@linux.dev \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.