Bug 847944
| Summary: | nfs_attr_use_mounted_on_file() returns wrong value [rhel-6.2.z] | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | RHEL Program Management <pm-rhel> |
| Component: | kernel | Assignee: | Frantisek Hrbata <fhrbata> |
| Status: | CLOSED ERRATA | QA Contact: | Jian Li <jiali> |
| Severity: | high | Docs Contact: | |
| Priority: | urgent | ||
| Version: | 6.4 | CC: | cww, dhoward, eguan, jiali, jlayton, nfs-maint, nmurray, pm-eus, rwheeler, steved |
| Target Milestone: | rc | Keywords: | ZStream |
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | kernel-2.6.32-220.26.1.el6 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2012-09-11 17:34:02 UTC | Type: | --- |
| 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: | 842312 | ||
| Bug Blocks: | |||
|
Description
RHEL Program Management
2012-08-14 07:14:07 UTC
I try to test this bug as (https://bugzilla.redhat.com/show_bug.cgi?id=842312#c13), but, kenrel-2.6.32-220.26.1.el6 diff from 2.6.32.293, so I couldn't only reproducer it in pre-patch kernel. In post-patch kernel, server are not able to work with fault-inject newpynfs. Because, kernel wouldn't fetch fs_locations which make (fattr->valid & NFS_ATTR_FATTR_V4_REFERRAL==1) when nfs_fhget is called which call nfs_attr_use_mounted_on_fileid. in fact, nfs_attr_use_mounted_on_fileid always return 0, whatever fattr4_mounted_on_file is used. If fattr4_fileid is not, nfs client couldn't create the inode for server's file, just as test result showed. 44 if (((fattr->valid & NFS_ATTR_FATTR_MOUNTED_ON_FILEID) == 0) || 45 ((fattr->valid & NFS_ATTR_FATTR_V4_REFERRAL) == 0)) Jeff, please check if I could verify this bug? 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-2012-1254.html |