it should've been "same structures being accessed by other threads" instead of "same structures are accessed by other threads"
*** Bug 1856 has been marked as a duplicate of this bug. ***
*** Bug 1857 has been marked as a duplicate of this bug. ***
*** Bug 1862 has been marked as a duplicate of this bug. ***
When glusterfs is terminated by an external command/program using a signal, sometimes glusterfs/d crashes, because of race-conditions between signal handling thread and other threads. Crashes are due to various reasons like private being set to NULL, transport being freed as part of cleanup process and same structures are accessed by other threads.
Found a crash on rdma too (gdb) p *this $1 = {ops = 0xbcc91f0, listener = 0x0, private = 0x0, xl_private = 0x0, xl = 0x2b5146f2a380, mydata = 0xbcc9028, lock = {__data = {__lock = 0, __count = 0, __owner = 0, __nusers = 0, __kind = -1, __spins = 0, __list = {__prev = 0x0, __next = 0x0}}, __size = '\0' <repeats 16 times>, "����", '\0' <repeats 19 times>, __align = 0}, refcount = 2, ctx = 0xbcc6010, options = 0xbcc8c08, name = 0xbcc94f8 "glusterf\020\003", dnscache = 0xbcc9cb8, buf = 0x0, init = 0x2aaaaad6eeaf <init>, fini = 0x2aaaaad6edbf <fini>, validate_options = 0, reconfigure = 0x2aaaaad6e6b9 <reconfigure>, notify = 0x2b5146f3c4a3 <rpc_clnt_notify>, notify_data = 0x0, peerinfo = {sockaddr = {ss_family = 2, __ss_align = 0, __ss_padding = '\0' <repeats 111 times>}, sockaddr_len = 16, identifier = "127.0.0.1:24007", '\0' <repeats 92 times>}, myinfo = { sockaddr = {ss_family = 2, __ss_align = 0, __ss_padding = '\0' <repeats 111 times>}, sockaddr_len = 16, identifier = "127.0.0.1:1020", '\0' <repeats 93 times>}, total_bytes_read = 2212, total_bytes_write = 828, list = {next = 0x0, prev = 0x0}} (gdb) p this->ops $2 = (struct rpc_transport_ops *) 0xbcc91f0 (gdb) p *this->ops $3 = {submit_request = 0, submit_reply = 0x311, connect = 0x3ece752e68 <main_arena+1160>, listen = 0x3ece752e68 <main_arena+1160>, disconnect = 0xbcc91f0, get_peername = 0xbcc91f0, get_peeraddr = 0, get_myname = 0, get_myaddr = 0} (gdb) p *this->ref There is no member named ref. (gdb) p *this->refcount Cannot access memory at address 0x2 (gdb)
*** Bug 1758 has been marked as a duplicate of this bug. ***
*** Bug 2032 has been marked as a duplicate of this bug. ***
*** Bug 1860 has been marked as a duplicate of this bug. ***
*** Bug 1879 has been marked as a duplicate of this bug. ***
*** Bug 2069 has been marked as a duplicate of this bug. ***
*** Bug 1837 has been marked as a duplicate of this bug. ***
*** Bug 1592 has been marked as a duplicate of this bug. ***
Please update the status of this bug as its been more than 6months since its filed (bug id < 2000) Please resolve it with proper resolution if its not valid anymore. If its still valid and not critical, move it to 'enhancement' severity.
Planing to keep 3.4.x branch as "internal enhancements" release without any features. So moving these bugs to 3.4.0 target milestone.
More of internal development, for future releases.
because of the large number of bugs filed against mainline version\ is ambiguous and about to be removed as a choice. If you believe this is still a bug, please change the status back to NEW and choose the appropriate, applicable version for it.