@marcan @dalias you keep underestimating the popularity of userspace choices that don't match yours.
@aep @marcan I think @marcan's point was that the affected buggy binaryware isn't linked with musl. Rather, musl users would just be affected by the broken syscall working around the broken binaryware.
@aep @marcan However as I said elsewhere in this thread I don't think there is broken binaryware. Any out there would be broken on every aarch64 system not just Asahi because the problem gets introduced at the call layer between the application and libc fcntl function, not at the syscall layer in some way that could vary by machine type.