Bug 843819 - Fix statedump code in nfs xlator
Summary: Fix statedump code in nfs xlator
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: nfs
Version: mainline
Hardware: All
OS: All
high
medium
Target Milestone: ---
Assignee: Vivek Agarwal
QA Contact: Saurabh
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-07-27 12:45 UTC by Pranith Kumar K
Modified: 2016-02-18 00:03 UTC (History)
4 users (show)

Fixed In Version: glusterfs-3.4.0
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-07-24 17:11:44 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:

Attachments (Terms of Use)

Description Pranith Kumar K 2012-07-27 12:45:58 UTC 
Description of problem:
remove gf_logs in statedump codepath.
locks acquired in statedump codepath should not be blocking. Please change the calls to try_lock variants.

This bug is logged because this xlator violates the above rules.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
Comment 1 Vijay Bellur 2012-11-24 15:09:51 UTC 
CHANGE: http://review.gluster.org/4193 (nfs: avoid blocking lock calls in statedump code) merged in master by Vijay Bellur (vbellur)
Note You need to log in before you can comment on or make changes to this bug.