[Bugs] [Bug 1234408] New: STACK_RESET may crash with concurrent statedump requests to a glusterfs process

[bugzilla at redhat.com]

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

            Bug ID: 1234408
           Summary: STACK_RESET may crash with concurrent statedump
                    requests to a glusterfs process
           Product: GlusterFS
           Version: 3.7.1
         Component: core
          Assignee: kparthas at redhat.com
          Reporter: kparthas at redhat.com
                CC: bugs at gluster.org, gluster-bugs at redhat.com
        Depends On: 1229658



+++ This bug was initially created as a clone of Bug #1229658 +++

Description of problem:
statedump requests that traverse call frames of all call stacks in execution
may race with a STACK_RESET on a stack. This could crash the corresponding
glusterfs process. For e.g, recently we observed this in a regression test
case, tests/basic/afr/sparse-self-heal.t.

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

How reproducible:
Intermittent

Steps to Reproduce:
1. Maintain constant I/O on a GlusterFS volume.
2. Issue a statedump request, using kill -SIGUSR1 <process-pid> concurrently.
3.

Actual results:
glusterfs process may crash

Expected results:
glusterfs process shouldn't crash and the statedump must be logged
successfully.

Additional info:

--- Additional comment from Anand Avati on 2015-06-09 07:43:20 EDT ---

REVIEW: http://review.gluster.org/11095 (stack: use list_head for managing
frames) posted (#5) for review on master by Krishnan Parthasarathi
(kparthas at redhat.com)


Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1229658
[Bug 1229658] STACK_RESET may crash with concurrent statedump requests to a
glusterfs process
-- 
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=mC17fMZW4I&a=cc_unsubscribe