[Bugs] [Bug 1212660] Crashes in logging code

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1212660

Jeff Darcy <jdarcy at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED



--- Comment #2 from Jeff Darcy <jdarcy at redhat.com> ---
This turns out to be a relative of both bug 1211749 and bug 1211473 - a memory
object allocated in a translator has persisted past the lifetime of that
translator.  The translator pointer in that memory object's header is therefore
no longer valid, and when the memory tracking code tries to dereference through
that pointer . . . BOOM.

In those other cases, the problem had to do with a temporary graph created for
option validation.  In this case it has to do with the list we use to detect
and coalesce duplicate log messages.  While the log_buf objects themselves are
allocated from a pool, various elements are copied via gf_strdup, using THIS
from the current context as the owning translator.  The solution is going to be
rather similar to that for 1211749:

    http://review.gluster.org/#/c/10238/

It's hacky, but it gets us past having our daemons blow up effectively at
random.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=Dnq4Fj6udJ&a=cc_unsubscribe