[Bugs] [Bug 1481199] mempool: run-time crash when built with --disable-mempool

[bugzilla at redhat.com]

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



--- Comment #6 from Worker Ant <bugzilla-bot at gluster.org> ---
COMMIT: https://review.gluster.org/18034 committed in master by Jeff Darcy
(jeff at pl.atyp.us) 
------
commit 3737ed53caad69ddb0f5b3db2e3498c2d7df2dff
Author: Niels de Vos <ndevos at redhat.com>
Date:   Fri Aug 18 17:12:05 2017 +0200

    mempool: fix code when GF_DISABLE_MEMPOOL is defined

    Problem: Run-time crash is observed when attempting to memset() a zero
    length buffer.

    Solution: When GF_DISABLE_MEMPOOL is set, mem_get() gets translated to a
    GF_MALLOC(). The size of the allocation does not need to relate to the
    available (but uninitialized) global memory pools. It is fine to
    allocate the exact amount of memory that was configured when the
    mem-pool was created.

    Change-Id: Iea0bff974bb771623a34d7a940e10cb0db0f90e1
    BUG: 1481199
    Reported-by: Milind Changire <mchangir at redhat.com>
    Signed-off-by: Niels de Vos <ndevos at redhat.com>
    Reviewed-on: https://review.gluster.org/18034
    Smoke: Gluster Build System <jenkins at build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins at build.gluster.org>
    Reviewed-by: Jeff Darcy <jeff at pl.atyp.us>

-- 
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=lx0NilnJZG&a=cc_unsubscribe