public inbox for bpf@vger.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,
	netdev@vger.kernel.org, bpf@vger.kernel.org
Subject: pull-request: bpf 2022-04-27
Date: Wed, 27 Apr 2022 23:27:48 +0200	[thread overview]
Message-ID: <20220427212748.9576-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 5 non-merge commits during the last 20 day(s) which contain
a total of 6 files changed, 34 insertions(+), 12 deletions(-).

The main changes are:

1) Fix xsk sockets when rx and tx are separately bound to the same umem, also
   fix xsk copy mode combined with busy poll, from Maciej Fijalkowski.

2) Fix BPF tunnel/collect_md helpers with bpf_xmit lwt hook usage which triggered
   a crash due to invalid metadata_dst access, from Eyal Birger.

3) Fix release of page pool in XDP live packet mode, from Toke Høiland-Jørgensen.

4) Fix potential NULL pointer dereference in kretprobes, from Adam Zabrocki.

   (Masami & Steven preferred this small fix to be routed via bpf tree given it's
    follow-up fix to Masami's rethook work that went via bpf earlier, too.)

Please consider pulling these changes from:

  git://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf.git

Thanks a lot!

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

Freysteinn Alfredsson, Magnus Karlsson, Masami Hiramatsu, Song Liu

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

The following changes since commit ec4eb8a86ade4d22633e1da2a7d85a846b7d1798:

  drivers: net: slip: fix NPD bug in sl_tx_timeout() (2022-04-06 23:00:16 -0700)

are available in the Git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf.git 

for you to fetch changes up to ba3beec2ec1d3b4fd8672ca6e781dac4b3267f6e:

  xsk: Fix possible crash when multiple sockets are created (2022-04-26 16:19:54 +0200)

----------------------------------------------------------------
Adam Zabrocki (1):
      kprobes: Fix KRETPROBES when CONFIG_KRETPROBE_ON_RETHOOK is set

Eyal Birger (1):
      bpf, lwt: Fix crash when using bpf_skb_set_tunnel_key() from bpf_xmit lwt hook

Maciej Fijalkowski (2):
      xsk: Fix l2fwd for copy mode + busy poll combo
      xsk: Fix possible crash when multiple sockets are created

Toke Høiland-Jørgensen (1):
      bpf: Fix release of page_pool in BPF_PROG_RUN in test runner

 include/net/xsk_buff_pool.h |  1 +
 kernel/kprobes.c            |  2 +-
 net/bpf/test_run.c          |  5 +++--
 net/core/lwt_bpf.c          |  7 +++----
 net/xdp/xsk.c               | 15 ++++++++++++++-
 net/xdp/xsk_buff_pool.c     | 16 ++++++++++++----
 6 files changed, 34 insertions(+), 12 deletions(-)

             reply	other threads:[~2022-04-27 21:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-27 21:27 Daniel Borkmann [this message]
2022-04-27 22:30 ` pull-request: bpf 2022-04-27 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=20220427212748.9576-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=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