public inbox for libstdc++-cvs@sourceware.org
help / color / mirror / Atom feed
* [gcc r13-5044] libstdc++: Fix deadlock in debug iterator increment [PR108288]
@ 2023-01-06 11:53 Jonathan Wakely
  0 siblings, 0 replies; only message in thread
From: Jonathan Wakely @ 2023-01-06 11:53 UTC (permalink / raw)
  To: gcc-cvs, libstdc++-cvs

https://gcc.gnu.org/g:b9479ddc7a28fb672ca67304a67d66524d8200a4

commit r13-5044-gb9479ddc7a28fb672ca67304a67d66524d8200a4
Author: Jonathan Wakely <jwakely@redhat.com>
Date:   Thu Jan 5 16:23:51 2023 +0000

    libstdc++: Fix deadlock in debug iterator increment [PR108288]
    
    With -fno-elide-constructors the debug iterator post-increment and
    post-decrement operators are susceptible to deadlock. They take a mutex
    lock and then return a temporary, which also attempts to take a lock to
    attach itself to the sequence. If the return value and *this happen to
    collide and use the same mutex from the pool, then you get a deadlock
    trying to lock a mutex that is already held by the current thread.
    
    The solution is to construct the return value before taking the lock.
    The copy constructor and pre-inc/pre-dec operators already manage locks
    correctly, without deadlock, so just implement post-inc/post-dec in the
    conventional way, taking a copy then modifying *this, then returning the
    copy.
    
    libstdc++-v3/ChangeLog:
    
            PR libstdc++/108288
            * include/debug/safe_iterator.h (_Safe_iterator::operator++(int))
            (_Safe_iterator::operator--(int)): Do not hold lock around
            construction of return value.

Diff:
---
 libstdc++-v3/include/debug/safe_iterator.h | 18 ++++++------------
 1 file changed, 6 insertions(+), 12 deletions(-)

diff --git a/libstdc++-v3/include/debug/safe_iterator.h b/libstdc++-v3/include/debug/safe_iterator.h
index 117dc93de60..f9068eaf8d6 100644
--- a/libstdc++-v3/include/debug/safe_iterator.h
+++ b/libstdc++-v3/include/debug/safe_iterator.h
@@ -761,12 +761,9 @@ namespace __gnu_debug
       _Safe_iterator
       operator++(int) _GLIBCXX_NOEXCEPT
       {
-	_GLIBCXX_DEBUG_VERIFY(this->_M_incrementable(),
-			      _M_message(__msg_bad_inc)
-			      ._M_iterator(*this, "this"));
-	__gnu_cxx::__scoped_lock __l(this->_M_get_mutex());
-	return _Safe_iterator(this->base()++, this->_M_sequence,
-			      _Attach_single());
+	_Safe_iterator __ret = *this;
+	++*this;
+	return __ret;
       }
 
       // ------ Bidirectional iterator requirements ------
@@ -788,12 +785,9 @@ namespace __gnu_debug
       _Safe_iterator
       operator--(int) _GLIBCXX_NOEXCEPT
       {
-	_GLIBCXX_DEBUG_VERIFY(this->_M_decrementable(),
-			      _M_message(__msg_bad_dec)
-			      ._M_iterator(*this, "this"));
-	__gnu_cxx::__scoped_lock __l(this->_M_get_mutex());
-	return _Safe_iterator(this->base()--, this->_M_sequence,
-			      _Attach_single());
+	_Safe_iterator __ret = *this;
+	--*this;
+	return __ret;
       }
 
       // ------ Random access iterator requirements ------

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2023-01-06 11:53 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-01-06 11:53 [gcc r13-5044] libstdc++: Fix deadlock in debug iterator increment [PR108288] Jonathan Wakely

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).