Finding the “second bug” in glibc’s condition variable
This seems like some really good debugging effort, kudos.But, my takeaway from this is that there’s a glibc bug which causes deadlocks in correct code, and a proposed fix (even if partial) has been available for years, and glibc still hasn’t shipped a version with the fix so it’s up to distros and users to patch the broken glibc code.Reminds me of how a glibc update broke GNU m4 and GNU didn’t ship a fix to m4 for years, so it was up to distros and users to patch the latest release of GNU m4 to make it compile with the latest version of GNU glibc.And then a couple of years later GNU shipped another version of glibc which broke m4.GNU doesn’t strike me as an organisation which places a lot of value on software quality and reliability.