summaryrefslogtreecommitdiffstats
path: root/ChangeLog
diff options
context:
space:
mode:
authorRainer Gerhards <rgerhards@adiscon.com>2008-09-18 12:19:33 +0200
committerRainer Gerhards <rgerhards@adiscon.com>2008-09-18 12:19:33 +0200
commit4c96ebdcfe075e80810b01257cf21ea1c9b3ec0e (patch)
treeb6768398d8d55c04e045b5213e11b952484025e8 /ChangeLog
parent988989e49ef8639123c83383ba256c4e67679c8d (diff)
downloadrsyslog-4c96ebdcfe075e80810b01257cf21ea1c9b3ec0e.tar.gz
rsyslog-4c96ebdcfe075e80810b01257cf21ea1c9b3ec0e.tar.xz
rsyslog-4c96ebdcfe075e80810b01257cf21ea1c9b3ec0e.zip
bugfix: potential race condition when adding messages to queue
There was a wrong order of mutex lock operations. It is hard to believe that really caused problems, but in theory it could and with threading we often see that theory becomes practice if something is only used long enough on a fast enough machine with enough CPUs ;)
Diffstat (limited to 'ChangeLog')
-rw-r--r--ChangeLog5
1 files changed, 5 insertions, 0 deletions
diff --git a/ChangeLog b/ChangeLog
index 125b0ada..23ac95fb 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -13,6 +13,11 @@ Version 3.21.5 [DEVEL] (rgerhards), 2008-09-??
local host as it knows itself.
- re-enabled gcc builtin atomic operations and added a proper
./configure check
+- bugfix: potential race condition when adding messages to queue
+ There was a wrong order of mutex lock operations. It is hard to
+ believe that really caused problems, but in theory it could and with
+ threading we often see that theory becomes practice if something is only
+ used long enough on a fast enough machine with enough CPUs ;)
---------------------------------------------------------------------------
Version 3.21.4 [DEVEL] (rgerhards), 2008-09-04
- removed compile time fixed message size limit (was 2K), limit can now