3 ms·
I don't think they're suggesting runtime use, but rather building software after the splice(2) change. That's how I read it at least.
by rootw0rm 4y ago
I don't think they're suggesting runtime use, but rather building software after the splice(2) change. That's how I read it at least.
- bonzini 4y agoIt would break if compiled on old kernel and run on new kernel. When CI is containerized the kernel might not even have anything to do with the distro that you're building on.
- vlovich123 4y agoAside from the “where you build isn’t where you run problem”, there’s the “this syscall doesn’t work when running on filesystem X or accessing /dev/urandom”. Not only is the autoconf solution not fixing the problem, it’s placing a massive undue burden on developers. Linus has been inconsistent here. Telemetry would have been helpful here in aiding this work (ie support it with the slow path but report the event so that distro maintainers could provide feedback on broken paths). Once you think you’ve eliminated the long tail of issues, then remove and see if anything remains broken that telemetry didn’t catch.