* Mathieu Desnoyers: > This is an RFC aiming for quick inclusion into the Linux kernel, unless > we prefer reverting the entire rseq glibc integration and try again in 6 > months. Their upcoming release is on August 3rd, so we need to take a > decision on this matter quickly. Just to clarify here, I don't think it's necessary to change glibc so that it only enables the rseq functionality if this particular bug is not present. From our perspective, it's just another kernel bug. If you truly feel we must not enable this feature in its present kernel state, then we need a working patch on all sides by the end of the week because the hard ABI freeze for glibc 2.32 is coming up, and at without any other patches, the only safe choice to prevent glibc from using slightly broken rseq support would be to back out the rseq patches. But again, I don't think such drastic action is necessary.
