6 Commits (d2abea093da443c9dcbf7943d62c48be7b6d9e0a)

Author	SHA1	Message	Date
Tamir Duberstein	d2abea093d	clippy: lint all bpf target archs	2 weeks ago
Tamir Duberstein	4ce1e29804	clippy.sh: build for BPF after everything else ... In cases where I run `./clippy.sh ... -p <crate>` I really want the results for that crate to come quickly.	3 weeks ago
Tamir Duberstein	fe99fa1d2e	ebpf: run clippy with target=bpf ... This build warnings from integration tests and makes `aya-ebpf`'s build script stricter.	1 month ago
Dave Tucker	3078e5aba0	chore: Fix clippy panic_handler warnings ... Working with aya in vscode will currently show a number of warnings along the lines of: ``` found duplicate lang item `panic_impl` the lang item is first defined in crate `std` (which `aya` depends on) ... second definition in the local crate (`bpf_probe_read`) ``` This comes from feature unification. integration-test requires the integration-common user feature, which requires aya, which in turn brings in std. For this same reason we avoid running clippy across the whole workspace. We can avoid this issue by using the panic handler from the another crate, which implements the same loop {} panic handler we use today. It seems rustc is happy to conditionally link the panic handler from an external crate without issuing warnings. Therefore, we add our own crate - ebpf-panic - for this purpose. Signed-off-by: Dave Tucker <dave@dtucker.co.uk>	8 months ago
Tamir Duberstein	e0c4948e36	Extract integration-common for shared types	11 months ago
Tamir Duberstein	fd00b39f09	Enable unwinding in userspace ... Unwinding gives us more information, so we shouldn't disable it globally. It is already disabled for BPF targets via the target configs in rustc itself. This complicates the clippy invocation somewhat, so put it in a shell script for developer as well as CI use.	11 months ago