Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1698566

Summary:	shd crashed while executing ./tests/bugs/core/bug-1432542-mpx-restart-crash.t in CI
Product:	[Community] GlusterFS	Reporter:	Sanju <srakonde>
Component:	selfheal	Assignee:	Mohammed Rafi KC <rkavunga>
Status:	CLOSED WORKSFORME	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	amukherj, bugs, rkavunga
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-05-14 07:33:23 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Sanju 2019-04-10 15:48:48 UTC

Description of problem:
core has generated by ./tests/bugs/core/bug-1432542-mpx-restart-crash.t in https://build.gluster.org/job/centos7-regression/5516/consoleFull

Version-Release number of selected component (if applicable):
mainline

Additional info:
From the core:
18:27:05 Core was generated by `/build/install/sbin/glusterfs -s localhost --volfile-id shd/patchy-vol02 -p /va'.
18:27:05 Program terminated with signal 11, Segmentation fault.
18:27:05 #0  0x00007f657903542f in gf_mem_set_acct_info (xl=0x7f65342cb5f0, alloc_ptr=0x7f656b2ec7c8, size=31, type=24, typestr=0x7f65790e3960 "gf_common_mt_asprintf") at /home/jenkins/root/workspace/centos7-regression/libglusterfs/src/mem-pool.c:54
18:27:05 54	    GF_ASSERT(type <= xl->mem_acct->num_types);

this means the memory has corrupted.

Thanks,
Sanju

Comment 1 Atin Mukherjee 2019-04-29 03:05:43 UTC

Rafi - could you take a look into it?

Comment 2 Mohammed Rafi KC 2019-05-14 07:33:23 UTC

This is most already fixed by the patch https://review.gluster.org/#/c/glusterfs/+/22468/. To verify this I ran the test in a loop overnight and I haven't seen any crash. So closing the bug.