chenhengqi@... writes: libbpf does not yet support attaching to TC hooks, but there is work in progress to add this. See https://lore.kernel.org/bpf/20210325120020.236504-4-memxor@... (

"Daniel Xu" <dxu@...> writes: Yeah, that's a RHEL version number (RHEL8.2 in this case, as seen by the "el8_2" bit). Which means that as far as features are concerned, the 4.18 version number is

#bcc

"Andrii Nakryiko" <andrii.nakryiko@...> writes: Yeah, that looks like a RHEL/CentOS kernel version number, which means the 4.18 bit is mostly fiction at this point (at least as far as BPF is con

#bcc

"Tristan Mayfield" <mayfieldtristan@...> writes: OK, I'll try to explain this one: Think of __builtin_memcpy() as a macro: it just compiles down to regular program instructions copying the memor

Ah, neat, didn't know that (and I tend to lump all that together mentally anyway). You're welcome, and thanks for confirming my understanding :) -Toke

"Tristan Mayfield" <mayfieldtristan@...> writes: Right, in that case that's probably just because the struct in question is next to some other valid memory (not sure where tracepoints keep their

"Tristan Mayfield" <mayfieldtristan@...> writes: bpf_probe_read() will happily read any piece of kernel memory, it doesn't respect kernel boundaries. So if the call succeeded (you did check the

Prashanth Fernando <prashanth.fernando@...> writes: You also need to compile a new version of iproute2 (where the 'tc' and 'ip' utilities come from). -Toke