diff options
author | Rainer Gerhards <rgerhards@adiscon.com> | 2009-08-19 13:05:42 +0200 |
---|---|---|
committer | Rainer Gerhards <rgerhards@adiscon.com> | 2009-08-19 13:05:42 +0200 |
commit | 7eb72ef77c8acbcc3d80644b9d3c5f15b44a9930 (patch) | |
tree | d9543e7470bfd29ca57e9bb76a7b9c63a7dcf138 | |
parent | 7d9ad618842dc16177844746dfe83126722f0c37 (diff) | |
download | rsyslog-7eb72ef77c8acbcc3d80644b9d3c5f15b44a9930.tar.gz rsyslog-7eb72ef77c8acbcc3d80644b9d3c5f15b44a9930.tar.xz rsyslog-7eb72ef77c8acbcc3d80644b9d3c5f15b44a9930.zip |
added important bug fix doc to current release
the bug fix was imported from 4.5.1, but it is important enough
to be highlighted in its own right.
-rw-r--r-- | ChangeLog | 10 |
1 files changed, 10 insertions, 0 deletions
@@ -2,6 +2,16 @@ Version 5.1.4 [DEVEL] (rgerhards), 2009-07-?? - bugfix: discard action did not work (did not discard messages) - bugfix: discard action caused segfault +- 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 5.1.3 [DEVEL] (rgerhards), 2009-07-28 - architecture change: queue now always has at least one worker thread |