Bug 838204
Summary: | Crash in posix_getxattr | ||
---|---|---|---|
Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Vijay Bellur <vbellur> |
Component: | glusterfs | Assignee: | Vijay Bellur <vbellur> |
Status: | CLOSED ERRATA | QA Contact: | Sachidananda Urs <surs> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 2.0 | CC: | gluster-bugs, rabhat, rfortier, sac, sdharane, vbellur |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | glusterfs-3.4.0qa4-1.el6rhs | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2013-09-23 22:32:44 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Vijay Bellur
2012-07-07 06:34:18 UTC
getxattr, removexattr and setxattr operations running parallely on a file (xattr is also same) will reproduce the crash. A patch (http://review.gluster.com/#change,3640) has been sent for this. Once it gets accepted in master, will be backported to release-3.3 branch. This bug is not seen in current master branch (which will get branched as RHS 2.1.0 soon). To consider it for fixing, want to make sure this bug still exists in RHS servers. If not reproduced, would like to close this. http://review.gluster.com/3673 and http://review.gluster.com/3681 fixes this bug also. Its fixed now. CHANGE: http://review.gluster.org/4319 (cluster/afr: check for the -ve values returned from dict_serialized_length) merged in master by Anand Avati (avati) Is not reproducible in glusterfs-3.4.0qa5. Ran a million parallel setfattr (setting and deleting xattrs) and getfattr operations. No crashes. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2013-1262.html |