[Bug nptl/20822] race condition in __lll_unlock_elision on powerpc

["cvs-commit at gcc dot gnu.org" <sourceware-bugzilla at sourceware dot org>]

https://sourceware.org/bugzilla/show_bug.cgi?id=20822

--- Comment #8 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "GNU C Library master sources".

The branch, release/2.23/master has been updated
       via  da9f68f2b9f653a49d0d0c6148d4649dc9ad7fd6 (commit)
      from  e9d53ff4d46e27d321161a2fb8f16820ea2cb68e (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=da9f68f2b9f653a49d0d0c6148d4649dc9ad7fd6

commit da9f68f2b9f653a49d0d0c6148d4649dc9ad7fd6
Author: Tulio Magno Quites Machado Filho <tuliom@linux.vnet.ibm.com>
Date:   Mon Jan 23 14:39:47 2017 -0200

    powerpc: Fix write-after-destroy in lock elision [BZ #20822]

    The update of *adapt_count after the release of the lock causes a race
    condition when thread A unlocks, thread B continues and destroys the
    mutex, and thread A writes to *adapt_count.

    (cherry picked from commit e9a96ea1aca4ebaa7c86e8b83b766f118d689d0f)
    (with changes from commit eb1321f291515dae75c83a40c39e775fdd38e97a)

-----------------------------------------------------------------------

Summary of changes:
 ChangeLog                                         |   13 +++++++++++++
 sysdeps/unix/sysv/linux/powerpc/elision-lock.c    |   10 +++++++---
 sysdeps/unix/sysv/linux/powerpc/elision-trylock.c |    7 ++++---
 sysdeps/unix/sysv/linux/powerpc/elision-unlock.c  |   15 +++++++++------
 4 files changed, 33 insertions(+), 12 deletions(-)

-- 
You are receiving this mail because:
You are on the CC list for the bug.