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 2023-11-30
Date: Thu, 30 Nov 2023 00:49:16 +0100 [thread overview]
Message-ID: <20231129234916.16128-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 7 day(s) which contain
a total of 10 files changed, 66 insertions(+), 15 deletions(-).
The main changes are:
1) Fix AF_UNIX splat from use after free in BPF sockmap, from John Fastabend.
2) Fix a syzkaller splat in netdevsim by properly handling offloaded programs (and
not device-bound ones), from Stanislav Fomichev.
3) Fix bpf_mem_cache_alloc_flags() to initialize the allocation hint, from Hou Tao.
4) Fix netkit by rejecting IFLA_NETKIT_PEER_INFO in changelink, from Daniel Borkmann.
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:
Jakub Kicinski, Jakub Sitnicki, Nikolay Aleksandrov, Yonghong Song
----------------------------------------------------------------
The following changes since commit d3fa86b1a7b4cdc4367acacea16b72e0a200b3d7:
Merge tag 'net-6.7-rc3' of git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net (2023-11-23 10:40:13 -0800)
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 51354f700d400e55b329361e1386b04695e6e5c1:
bpf, sockmap: Add af_unix test with both sockets in map (2023-11-30 00:25:25 +0100)
----------------------------------------------------------------
bpf-for-netdev
----------------------------------------------------------------
Daniel Borkmann (1):
netkit: Reject IFLA_NETKIT_PEER_INFO in netkit_change_link
Hou Tao (1):
bpf: Add missed allocation hint for bpf_mem_cache_alloc_flags()
John Fastabend (2):
bpf, sockmap: af_unix stream sockets need to hold ref for pair sock
bpf, sockmap: Add af_unix test with both sockets in map
Stanislav Fomichev (1):
netdevsim: Don't accept device bound programs
drivers/net/netdevsim/bpf.c | 4 +-
drivers/net/netkit.c | 6 +++
include/linux/skmsg.h | 1 +
include/net/af_unix.h | 1 +
kernel/bpf/memalloc.c | 2 +
net/core/skmsg.c | 2 +
net/unix/af_unix.c | 2 -
net/unix/unix_bpf.c | 5 +++
.../selftests/bpf/prog_tests/sockmap_listen.c | 51 +++++++++++++++++-----
.../selftests/bpf/progs/test_sockmap_listen.c | 7 +++
10 files changed, 66 insertions(+), 15 deletions(-)
next reply other threads:[~2023-11-29 23:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-29 23:49 Daniel Borkmann [this message]
2023-11-30 3:50 ` pull-request: bpf 2023-11-30 patchwork-bot+netdevbpf
2023-11-30 14:53 ` Eric Dumazet
2023-11-30 15:04 ` Daniel Borkmann
2023-11-30 15:54 ` John Fastabend
2023-11-30 16:04 ` Eric Dumazet
2023-11-30 16:19 ` Eric Dumazet
2023-11-30 23:37 ` John Fastabend
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=20231129234916.16128-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