[Bugs] [Bug 1475258] [Geo-rep]: Geo-rep hangs in changelog mode
bugzilla at redhat.com
bugzilla at redhat.com
Mon Jul 31 16:32:17 UTC 2017
https://bugzilla.redhat.com/show_bug.cgi?id=1475258
--- Comment #3 from Worker Ant <bugzilla-bot at gluster.org> ---
COMMIT: https://review.gluster.org/17915 committed in release-3.12 by
Shyamsundar Ranganathan (srangana at redhat.com)
------
commit c2742e4dd118e416fbd7fdf865350a5a3c92490c
Author: Niels de Vos <ndevos at redhat.com>
Date: Sun Jul 30 09:13:29 2017 +0200
mem-pool: track and verify initialization state
It is possible that pthread_getspecific() returns a non-NULL value in
case the pthread_key_t is not initialized. The behaviour for
pthread_getspecific() is not defined in this case. This can happen when
applications use mem-pools from libglusterfs.so, but did not call
mem_pools_init_early().
By tracking the status of the mem-pools initialization, it is now
possible to prevent calling pthread_getspecific() in case the
pthread_key_t is not initialized. In future, we might want to exend this
more to faciliate debugging.
Cherry picked from commit b5fa5ae05f73e03023db37e43fb203267b719160)
> Reported-by: Kotresh HR <khiremat at redhat.com>
> Tested-by: Jiffin Tony Thottan <jthottan at redhat.com>
> Change-Id: I6255419fe05792dc78b1eaff55bc008fc5ff3933
> Fixes: 1e8e62640 ("mem-pool: initialize pthread_key_t pool_key in
mem_pool_init_early()")
> BUG: 1475255
> Signed-off-by: Niels de Vos <ndevos at redhat.com>
> Reviewed-on: https://review.gluster.org/17899
> Smoke: Gluster Build System <jenkins at build.gluster.org>
> CentOS-regression: Gluster Build System <jenkins at build.gluster.org>
> Reviewed-by: jiffin tony Thottan <jthottan at redhat.com>
> Reviewed-by: Jeff Darcy <jeff at pl.atyp.us>
Change-Id: I6255419fe05792dc78b1eaff55bc008fc5ff3933
BUG: 1475258
Signed-off-by: Niels de Vos <ndevos at redhat.com>
Reviewed-on: https://review.gluster.org/17915
Smoke: Gluster Build System <jenkins at build.gluster.org>
CentOS-regression: Gluster Build System <jenkins at build.gluster.org>
Reviewed-by: Shyamsundar Ranganathan <srangana at redhat.com>
--
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=24MVvfWEoQ&a=cc_unsubscribe
More information about the Bugs
mailing list