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 2022-11-04
Date: Fri,  4 Nov 2022 01:04:45 +0100	[thread overview]
Message-ID: <20221104000445.30761-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 3 day(s) which contain
a total of 10 files changed, 113 insertions(+), 16 deletions(-).

The main changes are:

1) Fix memory leak upon allocation failure in BPF verifier's stack state
   tracking, from Kees Cook.

2) Fix address leakage when BPF progs release reference to an object, from Youlin Li.

3) Fix BPF CI breakage from buggy in.h uapi header dependency, from Andrii Nakryiko.

4) Fix bpftool pin sub-command's argument parsing, from Pu Lehui.

5) Fix BPF sockmap lockdep warning by cancelling psock work outside of socket
   lock, from Cong Wang.

6) Follow-up for BPF sockmap to fix sk_forward_alloc accounting, from Wang Yufen.

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:

Bill Wendling, Jakub Sitnicki, John Fastabend, Kees Cook, Quentin 
Monnet, Stanislav Fomichev, Zhengchao Shao

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

The following changes since commit 363a5328f4b0517e59572118ccfb7c626d81dca9:

  net: tun: fix bugs for oversize packet when napi frags enabled (2022-10-31 20:04:55 -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 475244f5e06beeda7b557d9dde46a5f439bf3379:

  selftests/bpf: Add verifier test for release_reference() (2022-11-04 00:24:29 +0100)

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

----------------------------------------------------------------
Andrii Nakryiko (2):
      net/ipv4: Fix linux/in.h header dependencies
      tools/headers: Pull in stddef.h to uapi to fix BPF selftests build in CI

Cong Wang (1):
      bpf, sock_map: Move cancel_work_sync() out of sock lock

Kees Cook (1):
      bpf, verifier: Fix memory leak in array reallocation for stack state

Pu Lehui (1):
      bpftool: Fix NULL pointer dereference when pin {PROG, MAP, LINK} without FILE

Wang Yufen (1):
      bpf, sockmap: Fix the sk->sk_forward_alloc warning of sk_stream_kill_queues

Youlin Li (2):
      bpf: Fix wrong reg type conversion in release_reference()
      selftests/bpf: Add verifier test for release_reference()

 include/linux/skmsg.h                              |  2 +-
 include/uapi/linux/in.h                            |  1 +
 kernel/bpf/verifier.c                              | 17 ++++++--
 net/core/skmsg.c                                   |  7 +---
 net/core/sock_map.c                                |  7 ++--
 net/ipv4/tcp_bpf.c                                 |  8 ++--
 tools/bpf/bpftool/common.c                         |  3 ++
 tools/include/uapi/linux/in.h                      |  1 +
 tools/include/uapi/linux/stddef.h                  | 47 ++++++++++++++++++++++
 .../testing/selftests/bpf/verifier/ref_tracking.c  | 36 +++++++++++++++++
 10 files changed, 113 insertions(+), 16 deletions(-)
 create mode 100644 tools/include/uapi/linux/stddef.h

             reply	other threads:[~2022-11-04  0:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-04  0:04 Daniel Borkmann [this message]
2022-11-04  4:10 ` pull-request: bpf 2022-11-04 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=20221104000445.30761-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