Message ID | 20220130115518.213259-1-jakub@cloudflare.com (mailing list archive) |
---|---|
Headers | show |
Series | Split bpf_sock dst_port field | expand |
On Sun, Jan 30, 2022 at 12:55:16PM +0100, Jakub Sitnicki wrote: > This is a follow-up to discussion around the idea of making dst_port in struct > bpf_sock a 16-bit field that happened in [1]. > > v2: > - use an anonymous field for zero padding (Alexei) Acked-by: Martin KaFai Lau <kafai@fb.com>
Hello: This series was applied to bpf/bpf-next.git (master) by Alexei Starovoitov <ast@kernel.org>: On Sun, 30 Jan 2022 12:55:16 +0100 you wrote: > This is a follow-up to discussion around the idea of making dst_port in struct > bpf_sock a 16-bit field that happened in [1]. > > v2: > - use an anonymous field for zero padding (Alexei) > > v1: > - keep dst_field offset unchanged to prevent existing BPF program breakage > (Martin) > - allow 8-bit loads from dst_port[0] and [1] > - add test coverage for the verifier and the context access converter > > [...] Here is the summary with links: - [bpf-next,v2,1/2] bpf: Make dst_port field in struct bpf_sock 16-bit wide https://git.kernel.org/bpf/bpf-next/c/4421a582718a - [bpf-next,v2,2/2] selftests/bpf: Extend verifier and bpf_sock tests for dst_port loads https://git.kernel.org/bpf/bpf-next/c/8f50f16ff39d You are awesome, thank you!