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,
	martin.lau@linux.dev, netdev@vger.kernel.org,
	bpf@vger.kernel.org
Subject: pull-request: bpf 2023-12-06
Date: Wed,  6 Dec 2023 23:05:28 +0100	[thread overview]
Message-ID: <20231206220528.12093-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 4 non-merge commits during the last 6 day(s) which contain
a total of 7 files changed, 185 insertions(+), 55 deletions(-).

The main changes are:

1) Fix race found by syzkaller on prog_array_map_poke_run when a BPF program's kallsym
   symbols were still missing, from Jiri Olsa.

2) Fix BPF verifier's branch offset comparison for BPF_JMP32 | BPF_JA, from Yonghong Song.

3) Fix xsk's poll handling to only set mask on bound xsk sockets, from Yewon Choi.

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:

Ilya Leoshkevich, Magnus Karlsson, Yonghong Song

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

The following changes since commit 830139e7b6911266a84a77e1f18abf758995cc89:

  octeontx2-af: Check return value of nix_get_nixlf before using nixlf (2023-12-01 12:19:02 +0000)

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 ffed24eff9e0e52d8e74df1c18db8ed43b4666e6:

  selftests/bpf: Add test for early update in prog_array_map_poke_run (2023-12-06 22:40:43 +0100)

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

----------------------------------------------------------------
Jiri Olsa (2):
      bpf: Fix prog_array_map_poke_run map poke update
      selftests/bpf: Add test for early update in prog_array_map_poke_run

Yewon Choi (1):
      xsk: Skip polling event check for unbound socket

Yonghong Song (1):
      bpf: Fix a verifier bug due to incorrect branch offset comparison with cpu=v4

 arch/x86/net/bpf_jit_comp.c                        | 46 ++++++++++++
 include/linux/bpf.h                                |  3 +
 kernel/bpf/arraymap.c                              | 58 +++------------
 kernel/bpf/core.c                                  | 12 ++--
 net/xdp/xsk.c                                      |  5 +-
 tools/testing/selftests/bpf/prog_tests/tailcalls.c | 84 ++++++++++++++++++++++
 tools/testing/selftests/bpf/progs/tailcall_poke.c  | 32 +++++++++
 7 files changed, 185 insertions(+), 55 deletions(-)
 create mode 100644 tools/testing/selftests/bpf/progs/tailcall_poke.c

             reply	other threads:[~2023-12-06 22:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-06 22:05 Daniel Borkmann [this message]
2023-12-07 17:50 ` pull-request: bpf 2023-12-06 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=20231206220528.12093-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