Re: mem_put without a xlator_t

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> I obseve a crash when rebalance process cannot start in tiered setup.
> It happens because the cleanup process calls mem_put() while xlator_t
> is not valid anymore. Here is the backtrace:

That looks closely related to the bug that was fixed by the
following patch:

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

In that case, the problem was with the allocation of members *within*
the log_buf.  In this case it's the allocation of the log_buf itself.
Looks like we just need to apply the same old_THIS trick in
log_buf_new.
_______________________________________________
Gluster-devel mailing list
Gluster-devel@xxxxxxxxxxx
http://www.gluster.org/mailman/listinfo/gluster-devel




[Index of Archives]     [Gluster Users]     [Ceph Users]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux