From: Cong Wang <xiyou.wangcong@gmail.com>
To: netdev@vger.kernel.org
Cc: bpf@vger.kernel.org, jiang.wang@bytedance.com,
duanxiongchun@bytedance.com, wangdongdong.6@bytedance.com,
Cong Wang <cong.wang@bytedance.com>
Subject: [Patch bpf-next v2 0/9] sockmap: add sockmap support to Unix datagram socket
Date: Mon, 19 Apr 2021 10:55:54 -0700 [thread overview]
Message-ID: <20210419175603.19378-1-xiyou.wangcong@gmail.com> (raw)
From: Cong Wang <cong.wang@bytedance.com>
This is the last patchset of the original large patchset. In the
previous patchset, a new BPF sockmap program BPF_SK_SKB_VERDICT
was introduced and UDP began to support it too. In this patchset,
we add BPF_SK_SKB_VERDICT support to Unix datagram socket, so that
we can finally splice Unix datagram socket and UDP socket. Please
check each patch description for more details.
To see the big picture, the previous patchsets are available:
https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next.git/commit/?id=1e0ab70778bd86a90de438cc5e1535c115a7c396
https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next.git/commit/?id=89d69c5d0fbcabd8656459bc8b1a476d6f1efee4
this patchset is also available:
https://github.com/congwang/linux/tree/sockmap3
---
v2: separate out from the original large patchset
rebase to the latest bpf-next
clean up unix_read_sock()
export sock_map_close()
factor out some helpers in selftests for code reuse
Cong Wang (9):
af_unix: implement ->read_sock() for sockmap
af_unix: implement ->psock_update_sk_prot()
af_unix: set TCP_ESTABLISHED for datagram sockets too
af_unix: implement unix_dgram_bpf_recvmsg()
sock_map: update sock type checks for AF_UNIX
selftests/bpf: factor out udp_socketpair()
selftests/bpf: factor out add_to_sockmap()
selftests/bpf: add a test case for unix sockmap
selftests/bpf: add test cases for redirection between udp and unix
MAINTAINERS | 1 +
include/net/af_unix.h | 13 +
net/core/sock_map.c | 9 +
net/unix/Makefile | 1 +
net/unix/af_unix.c | 82 +++-
net/unix/unix_bpf.c | 95 +++++
.../selftests/bpf/prog_tests/sockmap_listen.c | 386 ++++++++++++++----
7 files changed, 505 insertions(+), 82 deletions(-)
create mode 100644 net/unix/unix_bpf.c
--
2.25.1
next reply other threads:[~2021-04-19 17:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-19 17:55 Cong Wang [this message]
2021-04-19 17:55 ` [Patch bpf-next v2 1/9] af_unix: implement ->read_sock() for sockmap Cong Wang
2021-04-19 17:55 ` [Patch bpf-next v2 2/9] af_unix: implement ->psock_update_sk_prot() Cong Wang
2021-04-19 17:55 ` [Patch bpf-next v2 3/9] af_unix: set TCP_ESTABLISHED for datagram sockets too Cong Wang
2021-04-19 17:55 ` [Patch bpf-next v2 4/9] af_unix: implement unix_dgram_bpf_recvmsg() Cong Wang
2021-04-19 17:55 ` [Patch bpf-next v2 5/9] sock_map: update sock type checks for AF_UNIX Cong Wang
2021-04-19 17:56 ` [Patch bpf-next v2 6/9] selftests/bpf: factor out udp_socketpair() Cong Wang
2021-04-19 17:56 ` [Patch bpf-next v2 7/9] selftests/bpf: factor out add_to_sockmap() Cong Wang
2021-04-19 17:56 ` [Patch bpf-next v2 8/9] selftests/bpf: add a test case for unix sockmap Cong Wang
2021-04-19 17:56 ` [Patch bpf-next v2 9/9] selftests/bpf: add test cases for redirection between udp and unix Cong Wang
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=20210419175603.19378-1-xiyou.wangcong@gmail.com \
--to=xiyou.wangcong@gmail.com \
--cc=bpf@vger.kernel.org \
--cc=cong.wang@bytedance.com \
--cc=duanxiongchun@bytedance.com \
--cc=jiang.wang@bytedance.com \
--cc=netdev@vger.kernel.org \
--cc=wangdongdong.6@bytedance.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;
as well as URLs for NNTP newsgroup(s).