mirror of
https://github.com/torvalds/linux.git
synced 2026-06-05 04:56:13 +02:00
3882dccf48
Currently the only opportunity to set sock ops flags dictating which callbacks fire for a socket is from within a TCP-BPF sockops program. This is problematic if the connection is already set up as there is no further chance to specify callbacks for that socket. Add TCP_BPF_SOCK_OPS_CB_FLAGS to bpf_setsockopt() and bpf_getsockopt() to allow users to specify callbacks later, either via an iterator over sockets or via a socket-specific program triggered by a setsockopt() on the socket. Previous discussion on this here [1]. [1] https://lore.kernel.org/bpf/f42f157b-6e52-dd4d-3d97-9b86c84c0b00@oracle.com/ Signed-off-by: Alan Maguire <alan.maguire@oracle.com> Link: https://lore.kernel.org/r/20240808150558.1035626-2-alan.maguire@oracle.com Signed-off-by: Martin KaFai Lau <martin.lau@kernel.org> |
||
|---|---|---|
| .. | ||
| asm | ||
| asm-generic | ||
| io_uring | ||
| linux | ||
| nolibc | ||
| perf | ||
| tools | ||
| trace/events | ||
| uapi | ||
| vdso | ||