summaryrefslogtreecommitdiffstats
path: root/ChangeLog
diff options
context:
space:
mode:
authorRainer Gerhards <rgerhards@adiscon.com>2008-09-18 12:45:44 +0200
committerRainer Gerhards <rgerhards@adiscon.com>2008-09-18 12:45:44 +0200
commit9d8bb5629b6131be7c260ab3f9169ea1055c07f6 (patch)
treefa017f714eb4c75f94b9902f66c59f24d4bb4bf6 /ChangeLog
parent7b63cd6feda5087c43652bdcf8e694b544295d5b (diff)
parent4c96ebdcfe075e80810b01257cf21ea1c9b3ec0e (diff)
downloadrsyslog-9d8bb5629b6131be7c260ab3f9169ea1055c07f6.tar.gz
rsyslog-9d8bb5629b6131be7c260ab3f9169ea1055c07f6.tar.xz
rsyslog-9d8bb5629b6131be7c260ab3f9169ea1055c07f6.zip
Merge branch 'helgrind' into perf
Conflicts: ChangeLog
Diffstat (limited to 'ChangeLog')
-rw-r--r--ChangeLog7
1 files changed, 7 insertions, 0 deletions
diff --git a/ChangeLog b/ChangeLog
index c11d6aa8..85768cb7 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -13,6 +13,13 @@ Version 3.21.5 [DEVEL] (rgerhards), 2008-09-??
local host as it knows itself.
- doc bugfix: queue doc had wrong parameter name for setting controlling
worker thread shutdown period
+- 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