From 30927cb5306d01da2716786c2d9457c49ec49d0f Mon Sep 17 00:00:00 2001
From: Sebastian Falbesoner <sebastian.falbesoner@gmail.com>
Date: Sun, 16 Jan 2022 02:14:12 +0100
Subject: refactor: replace RecursiveMutex `m_subver_mutex` with Mutex

In each of the critical sections, only the the guarded variable is
accessed, without any chance that within one section another one is
called.  Hence, we can use an ordinary Mutex instead of RecursiveMutex.
---
 src/net.h | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

(limited to 'src/net.h')

diff --git a/src/net.h b/src/net.h
index 14c94c0319..c79abb91c3 100644
--- a/src/net.h
+++ b/src/net.h
@@ -434,7 +434,7 @@ public:
     //! Whether this peer is an inbound onion, i.e. connected via our Tor onion service.
     const bool m_inbound_onion;
     std::atomic<int> nVersion{0};
-    RecursiveMutex m_subver_mutex;
+    Mutex m_subver_mutex;
     /**
      * cleanSubVer is a sanitized string of the user agent byte array we read
      * from the wire. This cleaned string can safely be logged or displayed.
-- 
cgit v1.2.3