bpf

Seems we have some language features not fully documented (like bitshift operators in #1322).

Would be good to go through language grammar and make sure everything is in the reference guide.

Currently we have just one type of docs which are "reference" documentation. We should add a "how-to/tutorials" section with goal-driven content. We can start by drawing already available content:

https://blog.aquasec.com/kubernetes-runtime-security-ebpf
https://blog.aquasec.com/tracee-runtime-malware-alerts-aqua-postee
https://blog.aquasec.com/runtime-security-tracee-rules
https://github.co

At the moment of writing this issue, kubectl trace only supports X86-64 as target architecture.

The tool should be able to schedule bpftrace programs against all the architectures supported by bpftrace, that are X86-64 and arm64 (aarch64) see the Cmake definition.

To achieve that we n

Our eBPF code makes some arch-specific assumptions about the layout of struct pt_regs. We need to refactor this to use BPF CO-RE macros to make multi-arch support work properly for our kprobes.

This should work something like this:

From xtask:

cargo xtask integration-test --libbpf-dir ~/dev/libbpf -- -t tests::load::unload

On the integration-test side it's a flag -t that can be repeated multiple times to enable more tests...

integration-test -t tests::load::unload

Current situation

We execute kubectl-gadget using the columns format for integration tests and then we verify the output using regular expressions. The problem is that we are not currently verifying the type of all the fields because the current regular expressions do not match all the columns.

Impact

We could miss regressions on those fields that we are not verifying.

Prop

When solang --standard-json is run, the output from the compiler is in the standard json format. However, the input is not.

1. Parse input on stdin as json using the [standard json](https://docs.soliditylang.org/en/v0.8.13/using-the-compiler.html#compiler-input-and-output-json-descri

Minikube start

General Information

• Environment (minikube)
• Kernel version (Linux eswar-LEGION 5.13.0-52-generic #59~20.04.1-Ubuntu SMP Thu Jun 16 21:21:28 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux)

To Reproduce

1. Goto contributions minikube.
2. Install minikube and virtualbox using scripts mentioned under contributions/minikube dir.
3. Then run minikube with start_minik

Can we get some performance comparison between polycube and using standard linux facilities (NAT, iptables, etc.)?

CPU usage, PPS, latencies, etc.

https://github.com/aquasecurity/libbpfgo/blob/main/helpers/osinfo.go seems to be untested. It would be helpful to add some unit tests to cover certain scenarios.

nhi currently supports only systemd