BPF List
 help / color / mirror / Atom feed
From: Martin KaFai Lau <martin.lau@linux.dev>
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-next 2024-11-14
Date: Thu, 14 Nov 2024 12:28:32 -0800	[thread overview]
Message-ID: <20241114202832.3187927-1-martin.lau@linux.dev> (raw)

Hi David, hi Jakub, hi Paolo, hi Eric,

The following pull-request contains BPF updates for your *net-next* tree.

We've added 9 non-merge commits during the last 4 day(s) which contain
a total of 3 files changed, 226 insertions(+), 84 deletions(-).

The main changes are:

1) Fixes to bpf_msg_push/pop_data and test_sockmap. The changes has
   dependency on the other changes in the bpf-next/net branch,
   from Zijian Zhang.

2) Drop netns codes from mptcp test. Reuse the common helpers in
   test_progs, from Geliang Tang.

Please consider pulling these changes from:

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

Thanks a lot!

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

John Fastabend, Matthieu Baerts (NGI0)

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

The following changes since commit 8d1807a95c7dbb9633817fba776fa2f5e7c5146b:

  Merge branch 'mlx5-misc-patches-2024-10-31' (2024-11-03 15:37:17 -0800)

are available in the Git repository at:

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

for you to fetch changes up to 141b4d6a8049cecdc8124f87e044b83a9e80730d:

  Merge branch 'Fixes to bpf_msg_push/pop_data and test_sockmap' (2024-11-06 16:02:08 -0800)

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

----------------------------------------------------------------
Geliang Tang (1):
      selftests/bpf: Drop netns helpers in mptcp

Martin KaFai Lau (1):
      Merge branch 'Fixes to bpf_msg_push/pop_data and test_sockmap'

Zijian Zhang (8):
      selftests/bpf: Add txmsg_pass to pull/push/pop in test_sockmap
      selftests/bpf: Fix SENDPAGE data logic in test_sockmap
      selftests/bpf: Fix total_bytes in msg_loop_rx in test_sockmap
      selftests/bpf: Add push/pop checking for msg_verify_data in test_sockmap
      selftests/bpf: Add more tests for test_txmsg_push_pop in test_sockmap
      bpf, sockmap: Several fixes to bpf_msg_push_data
      bpf, sockmap: Several fixes to bpf_msg_pop_data
      bpf, sockmap: Fix sk_msg_reset_curr

 net/core/filter.c                              |  88 +++++++-----
 tools/testing/selftests/bpf/prog_tests/mptcp.c |  42 ++----
 tools/testing/selftests/bpf/test_sockmap.c     | 180 ++++++++++++++++++++++---
 3 files changed, 226 insertions(+), 84 deletions(-)

             reply	other threads:[~2024-11-14 20:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-14 20:28 Martin KaFai Lau [this message]
2024-11-15  3:30 ` pull-request: bpf-next 2024-11-14 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=20241114202832.3187927-1-martin.lau@linux.dev \
    --to=martin.lau@linux.dev \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --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