Linux sandbox: Allow rseq(2)
Glibc 2.32 (development version) registers rseq on thread startup. Because libraries' ELF constructors may see that rseq is registered, and it is unclear that libraries should have to deal with rseq deregistration, just allow it globally. Otherwise rseq registration status will be out of sync between threads which could cause unexpected issues. Hopefully different parts of Chrome will leverage it for fast per-cpu data. Bug: 1104160 Change-Id: I3f93ee598004910ffde46ee782ba60b6201ae8ca Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2298525 Commit-Queue: Matthew Denton <mpdenton@chromium.org> Reviewed-by:Robert Sesek <rsesek@chromium.org> Cr-Commit-Position: refs/heads/master@{#792128}
Showing
Please register or sign in to comment