Home
last modified time | relevance | path

Searched hist:"5 a52ae4e32a61ad06ef67f0b3123adbdbac4fb83" (Results 1 – 2 of 2) sorted by relevance

/openbmc/linux/include/net/
H A Dcls_cgroup.hdiff 5a52ae4e32a61ad06ef67f0b3123adbdbac4fb83 Fri Mar 27 10:58:53 CDT 2020 Daniel Borkmann <daniel@iogearbox.net> bpf: Allow to retrieve cgroup v1 classid from v2 hooks

Today, Kubernetes is still operating on cgroups v1, however, it is
possible to retrieve the task's classid based on 'current' out of
connect(), sendmsg(), recvmsg() and bind-related hooks for orchestrators
which attach to the root cgroup v2 hook in a mixed env like in case
of Cilium, for example, in order to then correlate certain pod traffic
and use it as part of the key for BPF map lookups.

Signed-off-by: Daniel Borkmann <daniel@iogearbox.net>
Signed-off-by: Alexei Starovoitov <ast@kernel.org>
Link: https://lore.kernel.org/bpf/555e1c69db7376c0947007b4951c260e1074efc3.1585323121.git.daniel@iogearbox.net
/openbmc/linux/net/core/
H A Dfilter.cdiff 5a52ae4e32a61ad06ef67f0b3123adbdbac4fb83 Fri Mar 27 10:58:53 CDT 2020 Daniel Borkmann <daniel@iogearbox.net> bpf: Allow to retrieve cgroup v1 classid from v2 hooks

Today, Kubernetes is still operating on cgroups v1, however, it is
possible to retrieve the task's classid based on 'current' out of
connect(), sendmsg(), recvmsg() and bind-related hooks for orchestrators
which attach to the root cgroup v2 hook in a mixed env like in case
of Cilium, for example, in order to then correlate certain pod traffic
and use it as part of the key for BPF map lookups.

Signed-off-by: Daniel Borkmann <daniel@iogearbox.net>
Signed-off-by: Alexei Starovoitov <ast@kernel.org>
Link: https://lore.kernel.org/bpf/555e1c69db7376c0947007b4951c260e1074efc3.1585323121.git.daniel@iogearbox.net