bpf.vger.kernel.org archive mirror
 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 2024-05-17
Date: Fri, 17 May 2024 02:16:00 +0200	[thread overview]
Message-ID: <20240517001600.23703-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 2 day(s) which contain
a total of 8 files changed, 20 insertions(+), 9 deletions(-).

The main changes are:

1) Fix KASAN slab-out-of-bounds in percpu_array_map_gen_lookup and add
   BPF selftests to cover this case, from Andrii Nakryiko.
   (Report https://lore.kernel.org/bpf/20240514231155.1004295-1-kuba@kernel.org/)

2) Fix two BPF selftests to adjust for kernel changes after fast-forwarding
   Linus' tree to make BPF CI all green again, from Martin KaFai Lau.

3) Fix libbpf feature detectors when using token_fd by adjusting the
   attribute size for memset to cover the former, also from Andrii Nakryiko.

4) Fix the description of 'src' in ALU instructions for the BPF ISA
   standardization doc, from Puranjay Mohan.

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:

Alan Maguire, Daniel Borkmann, Dave Thaler, Jakub Kicinski, Kumar 
Kartikeya Dwivedi, Zi Shen Lim

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

The following changes since commit 621cde16e49b3ecf7d59a8106a20aaebfb4a59a9:

  Merge git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next (2024-05-15 07:30:49 -0700)

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 51e2b8d33199df9675d2a36ec6aad0c27e91c6fe:

  selftests/bpf: Adjust btf_dump test to reflect recent change in file_operations (2024-05-17 01:50:11 +0200)

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

----------------------------------------------------------------
Andrii Nakryiko (3):
      libbpf: fix feature detectors when using token_fd
      bpf: save extended inner map info for percpu array maps as well
      selftests/bpf: add more variations of map-in-map situations

Martin KaFai Lau (2):
      selftests/bpf: Adjust test_access_variable_array after a kernel function name change
      selftests/bpf: Adjust btf_dump test to reflect recent change in file_operations

Puranjay Mohan (2):
      bpf, docs: Fix the description of 'src' in ALU instructions
      MAINTAINERS: Update ARM64 BPF JIT maintainer

 Documentation/bpf/standardization/instruction-set.rst          |  5 +++--
 MAINTAINERS                                                    |  2 +-
 kernel/bpf/map_in_map.c                                        |  4 ++--
 tools/lib/bpf/bpf.c                                            |  2 +-
 tools/lib/bpf/features.c                                       |  2 +-
 tools/testing/selftests/bpf/prog_tests/btf_dump.c              |  2 +-
 tools/testing/selftests/bpf/progs/map_kptr.c                   | 10 ++++++++++
 tools/testing/selftests/bpf/progs/test_access_variable_array.c |  2 +-
 8 files changed, 20 insertions(+), 9 deletions(-)

             reply	other threads:[~2024-05-17  0:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-17  0:16 Daniel Borkmann [this message]
2024-05-17  0:50 ` pull-request: bpf 2024-05-17 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=20240517001600.23703-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 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).