From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugzilla@gcc.gnu.org>
Received: by sourceware.org (Postfix, from userid 48)
 id EB1CC3858D28; Wed,  9 Feb 2022 20:31:10 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org EB1CC3858D28
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/104442] atomic<T>::wait incorrectly loops in case of
 spurious notification when __waiter is shared
Date: Wed, 09 Feb 2022 20:31:10 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 11.0
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cvs-commit at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-104442-4-xGlWi6EwNE@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-104442-4@http.gcc.gnu.org/bugzilla/>
References: <bug-104442-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: gcc-bugs@gcc.gnu.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Gcc-bugs mailing list <gcc-bugs.gcc.gnu.org>
List-Unsubscribe: <https://gcc.gnu.org/mailman/options/gcc-bugs>,
 <mailto:gcc-bugs-request@gcc.gnu.org?subject=unsubscribe>
List-Archive: <https://gcc.gnu.org/pipermail/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-request@gcc.gnu.org?subject=help>
List-Subscribe: <https://gcc.gnu.org/mailman/listinfo/gcc-bugs>,
 <mailto:gcc-bugs-request@gcc.gnu.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Feb 2022 20:31:11 -0000

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D104442

--- Comment #5 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Thomas Rodgers <rodgertq@gcc.gnu.org>:

https://gcc.gnu.org/g:4cf3c339815cdfa636b25a512f91b63d7c313fd6

commit r12-7151-g4cf3c339815cdfa636b25a512f91b63d7c313fd6
Author: Thomas Rodgers <rodgert@appliantology.com>
Date:   Wed Feb 9 12:29:19 2022 -0800

    libstdc++: Fix deadlock in atomic wait [PR104442]

    This issue was observed as a deadlock in
    29_atomics/atomic/wait_notify/100334.cc on vxworks. When a wait is
    "laundered" (e.g. type T* does not suffice as a waitable address for the
    platform's native waiting primitive), the address waited is that of the
    _M_ver member of __waiter_pool_base, so several threads may wait on the
    same address for unrelated atomic<T> objects. As noted in the PR, the
    implementation correctly exits the wait for the thread whose data
    changed, but not for any other threads waiting on the same address.

    As noted in the PR the __waiter::_M_do_wait_v member was correctly exit=
ing
    but the other waiters were not reloading the value of _M_ver before
    re-entering the wait.

    Moving the spin call inside the loop accomplishes this, and is
    consistent with the predicate accepting version of __waiter::_M_do_wait.

    libstdc++-v3/ChangeLog:

            PR libstdc++/104442
            * include/bits/atomic_wait.h (__waiter::_M_do_wait_v): Move spin
             loop inside do loop so that threads failing the wait, reload
             _M_ver.=