All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexei Starovoitov <alexei.starovoitov@gmail.com>
To: davem@davemloft.net
Cc: daniel@iogearbox.net, kuba@kernel.org, andrii@kernel.org,
	pabeni@redhat.com, edumazet@google.com, kafai@fb.com,
	netdev@vger.kernel.org, bpf@vger.kernel.org, kernel-team@fb.com
Subject: pull-request: bpf 2022-10-23
Date: Sun, 23 Oct 2022 12:22:44 -0700	[thread overview]
Message-ID: <20221023192244.81137-1-alexei.starovoitov@gmail.com> (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 18 day(s) which contain
a total of 8 files changed, 69 insertions(+), 5 deletions(-).

The main changes are:

1) Wait for busy refill_work when destroying bpf memory allocator, from Hou.

2) Allow bpf_user_ringbuf_drain() callbacks to return 1, from David.

3) Fix dispatcher patchable function entry to 5 bytes nop, from Jiri.

4) Prevent decl_tag from being referenced in func_proto, from Stanislav.

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:

Peter Zijlstra (Intel), Stanislav Fomichev, Yonghong Song

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

The following changes since commit 0326074ff4652329f2a1a9c8685104576bd8d131:

  Merge tag 'net-next-6.1' of git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next (2022-10-04 13:38:03 -0700)

are available in the Git repository at:

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

for you to fetch changes up to bed54aeb6ac1ced7e0ea27a82ee52af856610ff0:

  Merge branch 'Wait for busy refill_work when destroying bpf memory allocator' (2022-10-21 19:17:38 -0700)

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

----------------------------------------------------------------
Alexei Starovoitov (1):
      Merge branch 'Wait for busy refill_work when destroying bpf memory allocator'

Andrii Nakryiko (1):
      Merge branch 'Allow bpf_user_ringbuf_drain() callbacks to return 1'

David Vernet (2):
      bpf: Allow bpf_user_ringbuf_drain() callbacks to return 1
      selftests/bpf: Make bpf_user_ringbuf_drain() selftest callback return 1

Hou Tao (2):
      bpf: Wait for busy refill_work when destroying bpf memory allocator
      bpf: Use __llist_del_all() whenever possbile during memory draining

Jiri Olsa (1):
      bpf: Fix dispatcher patchable function entry to 5 bytes nop

Stanislav Fomichev (2):
      selftests/bpf: Add reproducer for decl_tag in func_proto return type
      bpf: prevent decl_tag from being referenced in func_proto

 arch/x86/net/bpf_jit_comp.c                            | 13 +++++++++++++
 include/linux/bpf.h                                    | 14 +++++++++++++-
 kernel/bpf/btf.c                                       |  5 +++++
 kernel/bpf/dispatcher.c                                |  6 ++++++
 kernel/bpf/memalloc.c                                  | 18 ++++++++++++++++--
 kernel/bpf/verifier.c                                  |  1 +
 tools/testing/selftests/bpf/prog_tests/btf.c           | 13 +++++++++++++
 .../testing/selftests/bpf/progs/user_ringbuf_success.c |  4 ++--
 8 files changed, 69 insertions(+), 5 deletions(-)

             reply	other threads:[~2022-10-23 19:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-23 19:22 Alexei Starovoitov [this message]
2022-10-24 18:20 ` pull-request: bpf 2022-10-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=20221023192244.81137-1-alexei.starovoitov@gmail.com \
    --to=alexei.starovoitov@gmail.com \
    --cc=andrii@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=kafai@fb.com \
    --cc=kernel-team@fb.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 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.