@d-e-s-o @ work

I think it would be helpful to have some kind of overview what synchronization assumptions libbpf C types make, but I couldn't find all that much information about that in...

I spoke with anakryiko (the `libbpf` maintainer). The basic stance seems to be: `libbpf` is not thread safe. Certain APIs likely are, if, say, they are just thin wrappers around...

> From what I could gather, there are two meanings for "atomic" which creates ambiguity and confusion. Yeah, the two are often mixed together. However, I believe it is a...

> But this commit haven't changed anything wrt clipboard or internals ¯_(ツ)_/¯... Right. What I am saying is that the issue got introduced somewhere between https://github.com/alacritty/alacritty/commit/8681f71084894db6d1e258be17db1f80bb669314 and [`v0.12.0`](https://github.com/alacritty/alacritty/tree/refs/tags/v0.12.0). It's hard...

`arm64` can be done similarly as we already do in CI: https://github.com/libbpf/libbpf-rs/blob/a2a62c39928b8825ce4424b02c3e4ad3865cba3f/.github/workflows/test.yml#L107-L136 Similar procedures will allow for compilation on different architectures. I don't believe we are familiar enough with Android...

@Rei-Tw @mdaverde If this is still an issue for you, please feel free to introduce an `attach_xdp_*` variant that accepts flags in a pull request. We have done something similar...

Fixed by https://github.com/libbpf/libbpf-rs/pull/625

> NOTE: this is totally API-breaking I think that is fine.

> Absent that, you end up with tests that need sudo, which isn't super necessary/desirable here IMHO Half our tests already require `sudo`.

@AlexZhao Others can correct me if my understanding is wrong, but `libbpf-rs` is expected to bind to a specific range of `libbpf` versions, and that is defined by `libbpf-sys`: https://github.com/libbpf/libbpf-sys#versioning...