diff options
author | Alexei Starovoitov <ast@kernel.org> | 2021-08-25 17:40:36 -0700 |
---|---|---|
committer | Alexei Starovoitov <ast@kernel.org> | 2021-08-25 17:40:36 -0700 |
commit | 0584e965fb2517f41b7057ffa26f3b6e15a53754 (patch) | |
tree | cad9561b3fc80ffe9254a66bcf36159a0d5141c8 /net/unix/af_unix.c | |
parent | 7d789bd0089ad2a6cc2315f281018bfafae820bc (diff) | |
parent | 574ee209286755ae57449196bfa11a90d2d724e5 (diff) |
Merge branch 'bpf: tcp: Allow bpf-tcp-cc to call bpf_(get|set)sockopt'
Martin KaFai says:
====================
This set allows the bpf-tcp-cc to call bpf_setsockopt. One use
case is to allow a bpf-tcp-cc switching to another cc during init().
For example, when the tcp flow is not ecn ready, the bpf_dctcp
can switch to another cc by calling setsockopt(TCP_CONGESTION).
bpf_getsockopt() is also added to have a symmetrical API, so
less usage surprise.
v2:
- Not allow switching to kernel's tcp_cdg because it is the only
kernel tcp-cc that stores a pointer to icsk_ca_priv.
Please see the commit log in patch 1 for details.
Test is added in patch 4 to check switching to tcp_cdg.
- Refactor the logic finding the offset of a func ptr
in the "struct tcp_congestion_ops" to prog_ops_moff()
in patch 1.
- bpf_setsockopt() has been disabled in release() since v1 (please
see commit log in patch 1 for reason). bpf_getsockopt() is
also disabled together in release() in v2 to avoid usage surprise
because both of them are usually expected to be available together.
bpf-tcp-cc can already use PTR_TO_BTF_ID to read from tcp_sock.
====================
Signed-off-by: Alexei Starovoitov <ast@kernel.org>
Diffstat (limited to 'net/unix/af_unix.c')
0 files changed, 0 insertions, 0 deletions