Bug 895841
| Summary: | [glusterfs-3.3.1qa3]: glusterfs client asserted | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Raghavendra Bhat <rabhat> |
| Component: | glusterd | Assignee: | Raghavendra Bhat <rabhat> |
| Status: | CLOSED ERRATA | QA Contact: | Sachidananda Urs <surs> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 2.0 | CC: | dblack, divya, gluster-bugs, grajaiya, joe.lin, rfortier, rhs-bugs, sac, shaines, storage-doc, vbellur |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | glusterfs-3.4.0qa8, glusterfs-3.3.0.5rhs-42 | Doc Type: | Bug Fix |
| Doc Text: |
Cause:
Because of some backend filesystem issue (xfs) lstat system call was getting 5 as returned valuse instead of either 0 for success or -1 for failure.
Consequence:
Since lstat's return value was checked only for -1, other non-zero value was assumed to be success and success was returned to other xlators. But the fop was a filed fop and many of the pointers were NULL. When some other component got success and accessed one of the pointers, the process crashed.
Fix:
Fix is check for 0 after lstat call and any value other than 0 is treated as a failure and the same is returned to the other components.
Result:
Now if there is a backend failure and a system call returns some value other that 0 or -1, then that system call is treated as failure and error is returned to the application.
|
Story Points: | --- |
| Clone Of: | 864401 | Environment: | |
| Last Closed: | 2013-03-28 22:28:36 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: | |||
| Bug Depends On: | 864401 | ||
| Bug Blocks: | |||
|
Description
Raghavendra Bhat
2013-01-16 05:54:01 UTC
Fixed in version and step to verify please. Moving to modified as the patch has been accepted. Steps to reproduce: Simulate a backend xfs failure such that when a system call(lstat in this case) is executed instead of 0 (for success) or -1 (for failure) some other value is be returned. Raghavendra, This bug has been added to Update 4 errata. Could you provide your inputs in doc text field which will enable me to update errata?? Thanks, Divya Marking the bug as resolved, unable to reproduce the issue. Tried with NFS and FUSE clients on the volume. Was not able to induce the crash. 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/RHSA-2013-0691.html |