6 Commits (5cccaa57b201f78ac56baafcd903cc9b6f29e45d)

Author	SHA1	Message	Date
Michal R	98e8c78376	aya-ebpf: Make use of `Borrow` and `BorrowMut` in map methods ... Let callers pass either owned objects or references. We do that already in the user-space methods.	2 months ago
Tamir Duberstein	5f5305c2a8	lint all crates; enable strict pointer lints	3 months ago
dependabot[bot]	c0ff1aa0cc	build(deps): update network-types requirement in the cargo-crates group ... Updates the requirements on [network-types](https://github.com/vadorovsky/network-types) to permit the latest version. Updates `network-types` to 0.0.7 - [Release notes](https://github.com/vadorovsky/network-types/releases) - [Changelog](https://github.com/vadorovsky/network-types/blob/main/CHANGELOG.md) - [Commits](https://github.com/vadorovsky/network-types/compare/v0.0.7...v0.0.7) --- updated-dependencies: - dependency-name: network-types dependency-version: 0.0.7 dependency-type: direct:production dependency-group: cargo-crates ... Signed-off-by: dependabot[bot] <support@github.com>	8 months 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>	9 months ago
Tamir Duberstein	f0a9f19ddc	Bump edition to 2024 ... Change FromRawTracepointArgs::arg to return T rather than *const T which seems to have been returning a dangling pointer. Arguably this is not strictly necessary; edition 2024 seems to be focused on increased strictness around unsafe code which doesn't unlock new functionality for our users. That said, this work revealed an apparent bug (see above) that we wouldn't otherwise catch due to allow-by-default lints.	10 months ago
Wouter Dullaert	fb0a339adf	feat(aya-ebpf): Add integration test for memmove implementation	1 year ago