+++ This bug was initially created as a clone of Bug #1727068 +++ 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: 1. 2. 3. 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:
REVIEW: https://review.gluster.org/23046 (core: fix deadlock between statedump and fd_anonymous()) posted (#1) for review on release-7 by Xavi Hernandez
REVIEW: https://review.gluster.org/23046 (core: fix deadlock between statedump and fd_anonymous()) merged (#2) on release-7 by Rinku Kothiya