[syslog-ng] [Bug 139] syslog-ng crashes on SIGHUP when rewrite used in multiple log{} declarations

[bugzilla at bugzilla.balabit.com]

https://bugzilla.balabit.com/show_bug.cgi?id=139


Balazs Scheidler <bazsi at balabit.hu> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|                            |FIXED
             Status|NEW                         |RESOLVED




--- Comment #3 from Balazs Scheidler <bazsi at balabit.hu>  2011-10-23 09:08:52 ---
Committed this patch which seems to fix it for me:

commit 46bbdf9a107409e320450f9c4b6a82c2cf9f36af
Author: Balazs Scheidler <bazsi at balabit.hu>
Date:   Sun Oct 23 09:08:08 2011 +0200

    LogMatcher: fixed reference counting

    A reference count was added to LogMatcher instances, but it contained several
    critical issues:
      - the refcount wasn't initialized
      - the instance got freed when the refcount was non-zero

    Essentially the only case it worked when a rewrite rule was referenced
    from only _one_ location and in that case it leaked the matcher instance.

    Kudos for the great diagnosis in the original report, reported as ticket
    #139 in bugzilla.balabit.com.

    Reported-By: Patrick <bugzilla.syslogng at feystorm.net>
    Cc: syslog-ng-stable at balabit.com
    Signed-off-by: Balazs Scheidler <bazsi at balabit.hu>


-- 
Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.