[Bugs] [Bug 1539603] New: Glusterfs crash when doing statedump with memory accounting is disabled

bugzilla at redhat.com bugzilla at redhat.com
Mon Jan 29 09:56:52 UTC 2018


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

            Bug ID: 1539603
           Summary: Glusterfs crash when doing statedump with memory
                    accounting is disabled
           Product: GlusterFS
           Version: 3.13
         Component: libglusterfsclient
          Assignee: bugs at gluster.org
          Reporter: kinglongmee at gmail.com
                CC: bugs at gluster.org



Description of problem:
Program terminated with signal 11, Segmentation fault.
#0  0x00007fe24cff543a in gf_proc_dump_xlator_mem_info_only_in_use
(xl=0x7fe23e44dc00) at statedump.c:269
269             gf_proc_dump_write ("num_types", "%d",
xl->mem_acct->num_types);
Missing separate debuginfos, use: debuginfo-install glibc-2.17-157.el7.x86_64
jemalloc-3.6.0-1.el7.x86_64 keyutils-libs-1.5.8-3.el7.x86_64
krb5-libs-1.14.1-26.el7.x86_64 libcom_err-1.42.9-9.el7.x86_64
libgcc-4.8.5-11.el7.x86_64 libselinux-2.5-6.el7.x86_64
libuuid-2.23.2-33.el7.x86_64 openssl-libs-1.0.1e-60.el7.x86_64
pcre-8.32-15.el7_2.1.x86_64 zlib-1.2.7-17.el7.x86_64
(gdb) bt
#0  0x00007fe24cff543a in gf_proc_dump_xlator_mem_info_only_in_use
(xl=0x7fe23e44dc00) at statedump.c:269
#1  0x00007fe24cff6310 in gf_proc_dump_oldgraph_xlator_info
(top=0x7fe23e44dc00) at statedump.c:530
#2  0x00007fe24cff7114 in gf_proc_dump_info (signum=10, ctx=0x7fe24ac0e000) at
statedump.c:845
#3  0x00007fe24d4d4bab in glusterfs_sigwaiter (arg=0x7ffc6c080750) at
glusterfsd.c:2109
#4  0x00007fe24bbd5dc5 in start_thread () from /lib64/libpthread.so.0
#5  0x00007fe24b51a73d in clone () from /lib64/libc.so.6
(gdb) p xl->mem_acct
$1 = (struct mem_acct *) 0x0
(gdb) p xl->mem_acct->rec
$2 = 0x10
(gdb)


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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.


More information about the Bugs mailing list