No description. Add one?
- C 52.6%
- Rust 25.3%
- C++ 22.1%
| Filename | Latest commit message | Latest commit date |
|---|---|---|
4f6573959b
Long term we don't even want reset() to exist. It's simply not useful since only the bpfloader can create maps, and thus all we can do is construct from pre-existing pinned bpf path - and we should never destroy/unpin/delete these. Similarly the move constructor is probably spurious. Basically the only real use for reset() is in tests, and even there the overall utility is not clear. Hence, in the mean time, make it harder to use incorrectly, and harder to use in general. To do that we get rid of reset() -> you must call reset(-1) and we eliminate the ability to call reset(unique_fd) which has unclear fd-leaking semantics. Also remove a spot where it is called spuriously. Test: build, atest Bug: 129773125 Signed-off-by: Maciej Żenczykowski <maze@google.com> Change-Id: Ia018224aca0005ab68809b350595485ccd3f1bd3 |
||
| bpfloader | ||
| libbpf_android | ||
| progs | ||
| .clang-format | ||
| Android.bp | ||
| MODULE_LICENSE_APACHE2 | ||
| NOTICE | ||
| OWNERS | ||
| PREUPLOAD.cfg | ||