diff options
| author | Alan Maguire <[email protected]> | 2024-08-08 15:05:57 +0000 |
|---|---|---|
| committer | Martin KaFai Lau <[email protected]> | 2024-08-08 23:52:43 +0000 |
| commit | 3882dccf48f9fbe787b5df3187d708ef348ac860 (patch) | |
| tree | d37cabf5f0ea4cd40b79467cd6903bb95954e0bc /tools/testing/selftests/bpf/prog_tests/sockmap_basic.c | |
| parent | net: mvpp2: Increase size of queue_name buffer (diff) | |
| download | kernel-3882dccf48f9fbe787b5df3187d708ef348ac860.tar.gz kernel-3882dccf48f9fbe787b5df3187d708ef348ac860.zip | |
bpf/bpf_get,set_sockopt: add option to set TCP-BPF sock ops flags
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/[email protected]/
Signed-off-by: Alan Maguire <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Martin KaFai Lau <[email protected]>
Diffstat (limited to 'tools/testing/selftests/bpf/prog_tests/sockmap_basic.c')
0 files changed, 0 insertions, 0 deletions
