public inbox for bpf@vger.kernel.org
 help / color / mirror / Atom feed
From: Martin KaFai Lau <martin.lau@linux.dev>
To: David Miller <davem@davemloft.net>,
	Jakub Kicinski <kuba@kernel.org>,
	Eric Dumazet <edumazet@google.com>,
	Paolo Abeni <pabeni@redhat.com>
Cc: Alexei Starovoitov <ast@kernel.org>,
	Andrii Nakryiko <andrii@kernel.org>,
	Daniel Borkmann <daniel@iogearbox.net>,
	Martin KaFai Lau <martin.lau@kernel.org>,
	netdev@vger.kernel.org, bpf@vger.kernel.org
Subject: pull-request: bpf-next 2025-03-06
Date: Thu,  6 Mar 2025 21:53:35 -0800	[thread overview]
Message-ID: <20250307055335.441298-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 6 non-merge commits during the last 13 day(s) which contain
a total of 6 files changed, 230 insertions(+), 56 deletions(-).

The main changes are:

1) Add XDP metadata support for tun driver, from Marcus Wichelmann.

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:

Jason Wang, Willem de Bruijn

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

The following changes since commit b66e19dcf684b21b6d3a1844807bd1df97ad197a:

  Merge branch 'mctp-add-mctp-over-usb-hardware-transport-binding' (2025-02-21 16:45:26 -0800)

are available in the Git repository at:

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

for you to fetch changes up to 72aad21de5f65bea60c3064ad463b3793fb4b1c6:

  Merge branch 'xdp-metadata-support-for-tun-driver' (2025-03-06 12:31:09 -0800)

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

----------------------------------------------------------------
Marcus Wichelmann (6):
      net: tun: Enable XDP metadata support
      net: tun: Enable transfer of XDP metadata to skb
      selftests/bpf: Move open_tuntap to network helpers
      selftests/bpf: Refactor xdp_context_functional test and bpf program
      selftests/bpf: Add test for XDP metadata support in tun driver
      selftests/bpf: Fix file descriptor assertion in open_tuntap helper

Martin KaFai Lau (1):
      Merge branch 'xdp-metadata-support-for-tun-driver'

 drivers/net/tun.c                                  |  28 +++-
 tools/testing/selftests/bpf/network_helpers.c      |  28 ++++
 tools/testing/selftests/bpf/network_helpers.h      |   3 +
 .../testing/selftests/bpf/prog_tests/lwt_helpers.h |  29 -----
 .../bpf/prog_tests/xdp_context_test_run.c          | 145 ++++++++++++++++++++-
 tools/testing/selftests/bpf/progs/test_xdp_meta.c  |  53 +++++---
 6 files changed, 230 insertions(+), 56 deletions(-)

             reply	other threads:[~2025-03-07  5:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-07  5:53 Martin KaFai Lau [this message]
2025-03-08  3:40 ` pull-request: bpf-next 2025-03-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=20250307055335.441298-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=martin.lau@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