[Bugs] [Bug 1727068] New: Deadlock when generating statedumps

bugzilla at redhat.com bugzilla at redhat.com
Thu Jul 4 11:12:29 UTC 2019


            Bug ID: 1727068
           Summary: Deadlock when generating statedumps
           Product: GlusterFS
           Version: 4.1
            Status: NEW
         Component: core
          Assignee: bugs at gluster.org
          Reporter: jahernan at redhat.com
                CC: bugs at gluster.org
  Target Milestone: ---
    Classification: Community

Description of problem:

There seems to be a deadlock between statedump generation and creation of an
anonymous fd.

When a statedump is generated and it's going to dump inode information, it
takes the inode table lock and then each individual inode lock.

On the other side, when an anonymous fd is created, first it's acquired the
lock from the inode, and then the lock from the inode table when the refcount
of the inode is incremented.

This causes a deadlock because of reverse acquisition order of the locks.

This deadlock may not be exclusive of statedump, but there are few places where
we take both locks at the same time, and for sure none of them does that in a
so "massive" way.

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

How reproducible:

It's a race hard to reproduce.

Steps to Reproduce:

Actual results:

Generation of statedump hangs and mount point becomes unresponsiveness.

Expected results:

Generation of statedump should complete successfully and mount point continue
working normally.

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