aboutsummaryrefslogtreecommitdiff
path: root/src/net_processing.cpp
diff options
context:
space:
mode:
authorCory Fields <cory-nospam-@coryfields.com>2016-12-31 02:05:36 -0500
committerCory Fields <cory-nospam-@coryfields.com>2017-01-12 23:08:08 -0500
commite60360e139852c655930e99d4bb4db554cd8385e (patch)
treeadfb51a4f75f327b713de79412fa75c7292f7db0 /src/net_processing.cpp
parent991955ee81034dc3fbc1c2a8e60c04fc9e0b538c (diff)
net: remove cs_vRecvMsg
vRecvMsg is now only touched by the socket handler thread. The accounting vars (nRecvBytes/nLastRecv/mapRecvBytesPerMsgCmd) are also only used by the socket handler thread, with the exception of queries from rpc/gui. These accesses are not threadsafe, but they never were. This needs to be addressed separately. Also, update comment describing data flow
Diffstat (limited to 'src/net_processing.cpp')
-rw-r--r--src/net_processing.cpp1
1 files changed, 0 insertions, 1 deletions
diff --git a/src/net_processing.cpp b/src/net_processing.cpp
index 185ab980fe..32a5862f26 100644
--- a/src/net_processing.cpp
+++ b/src/net_processing.cpp
@@ -2439,7 +2439,6 @@ bool static ProcessMessage(CNode* pfrom, string strCommand, CDataStream& vRecv,
return true;
}
-// requires LOCK(cs_vRecvMsg)
bool ProcessMessages(CNode* pfrom, CConnman& connman, std::atomic<bool>& interruptMsgProc)
{
const CChainParams& chainparams = Params();