There's documentation at [1] of crashes in at least three different
applications being avoided by disabling lock elision. Rebuilding glibc is
restrictive for a lot of the impacted users. I'd be in favor of any of the
following solutions:
a) disabling lock elision by default
b) providing a mean
Curiously, the patchwork comments there point to kernels << 4.2 being
the major cause of the performance regressions brought about by TLE.
Was it actually 16.04 customers (on 16.04 kernels) that caused this bug
to be opened, or was it that you identified the issue on RedHat and then
proposed the pa
The above comment aside, we might end up disabling lock elision on *all*
the architectures that support it due to fears of broken software in the
wild that violates pthread double-unlock rules, something only coming to
light recently due to ppc64el/s390x users being very much in a minority,
and x86
It looks like this has never been integrated?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1560634
Title:
[Ubuntu 16.04.1] Provide a way to dynamically enable lock elision on
glibc
To manage not
Adam, please evaluate for 16.04. Thanks!
** Package changed: ubuntu => glibc (Ubuntu)
** Changed in: glibc (Ubuntu)
Importance: Undecided => Medium
** Changed in: glibc (Ubuntu)
Status: New => Triaged
** Changed in: glibc (Ubuntu)
Milestone: None => ubuntu-16.04
** Changed in: g
