diff options
| author | Niels de Vos <ndevos@redhat.com> | 2017-08-18 17:12:05 +0200 |
|---|---|---|
| committer | Jeff Darcy <jeff@pl.atyp.us> | 2017-09-02 02:21:15 +0000 |
| commit | 3737ed53caad69ddb0f5b3db2e3498c2d7df2dff (patch) | |
| tree | a0ff5871403fc4b42de675b6814c8d45cb5eb29d /doc | |
| parent | d7ccdb33c2e84bab25bf0898866104f8a85b4217 (diff) | |
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@redhat.com>
Signed-off-by: Niels de Vos <ndevos@redhat.com>
Reviewed-on: https://review.gluster.org/18034
Smoke: Gluster Build System <jenkins@build.gluster.org>
CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
Reviewed-by: Jeff Darcy <jeff@pl.atyp.us>
Diffstat (limited to 'doc')
0 files changed, 0 insertions, 0 deletions