summaryrefslogtreecommitdiffstats
path: root/ChangeLog
diff options
context:
space:
mode:
authorRainer Gerhards <rgerhards@adiscon.com>2009-08-19 13:04:35 +0200
committerRainer Gerhards <rgerhards@adiscon.com>2009-08-19 13:04:35 +0200
commit7d9ad618842dc16177844746dfe83126722f0c37 (patch)
tree0639aa1d81150c17f3b20530ad2538f8d325ddae /ChangeLog
parentdfc2b538ecdcd70a2ae091ad529a4972a91e3aa1 (diff)
parent16fb5cd701d4c12f8ad573dde8ff52c9eaecb79f (diff)
downloadrsyslog-7d9ad618842dc16177844746dfe83126722f0c37.tar.gz
rsyslog-7d9ad618842dc16177844746dfe83126722f0c37.tar.xz
rsyslog-7d9ad618842dc16177844746dfe83126722f0c37.zip
Merge branch 'beta'
Diffstat (limited to 'ChangeLog')
-rw-r--r--ChangeLog10
1 files changed, 10 insertions, 0 deletions
diff --git a/ChangeLog b/ChangeLog
index f0018e74..fdbf45cf 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -88,6 +88,16 @@ Version 4.5.2 [DEVEL] (rgerhards), 2009-07-??
does most probably not have any effect in practice.
- bugfix: if tcp listen port could not be created, no error message was
emitted
+- bugfix: potential segfault in output file writer (omfile)
+ In async write mode, we use modular arithmetic to index the output
+ buffer array. However, the counter variables accidently were signed,
+ thus resulting in negative indizes after integer overflow. That in turn
+ could lead to segfaults, but was depending on the memory layout of
+ the instance in question (which in turn depended on a number of
+ variables, like compile settings but also configuration). The counters
+ are now unsigned (as they always should have been) and so the dangling
+ mis-indexing does no longer happen. This bug potentially affected all
+ installations, even if only some may actually have seen a segfault.
---------------------------------------------------------------------------
Version 4.5.1 [DEVEL] (rgerhards), 2009-07-15
- CONFIG CHANGE: $HUPisRestart default is now "off". We are doing this