diff options
| author | Albert Fluegel <af@muc.de> | 2013-11-18 12:18:01 -0500 |
|---|---|---|
| committer | J. Bruce Fields <bfields@redhat.com> | 2013-12-10 20:35:58 -0500 |
| commit | 6e14b46b91fee8a049b0940333ce13a820beaaa5 (patch) | |
| tree | 6531f1a4613ade90ae007afa76557b27a455f30b /fs/nfsd/nfs3xdr.c | |
| parent | 4bd8eabc29e17d9b29cee16077e1621e209a1b27 (diff) | |
| download | linux-stable-6e14b46b91fee8a049b0940333ce13a820beaaa5.tar.gz linux-stable-6e14b46b91fee8a049b0940333ce13a820beaaa5.tar.bz2 linux-stable-6e14b46b91fee8a049b0940333ce13a820beaaa5.zip | |
nfsd: don't return high mode bits
The Linux NFS server replies among other things to a "Check access permission"
the following:
NFS: File type = 2 (Directory)
NFS: Mode = 040755
A netapp server replies here:
NFS: File type = 2 (Directory)
NFS: Mode = 0755
The RFC 1813 i read:
fattr3
struct fattr3 {
ftype3 type;
mode3 mode;
uint32 nlink;
...
For the mode bits only the lowest 9 are defined in the RFC
As far as I can tell, knfsd has always done this, so apparently it's harmless.
Nevertheless, it appears to be wrong.
Note this is already correct in the NFSv4 case, only v2 and v3 need
fixing.
Signed-off-by: J. Bruce Fields <bfields@redhat.com>
Diffstat (limited to 'fs/nfsd/nfs3xdr.c')
| -rw-r--r-- | fs/nfsd/nfs3xdr.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/fs/nfsd/nfs3xdr.c b/fs/nfsd/nfs3xdr.c index 14d9ecb96cff..1ee6baec5fa1 100644 --- a/fs/nfsd/nfs3xdr.c +++ b/fs/nfsd/nfs3xdr.c @@ -168,7 +168,7 @@ encode_fattr3(struct svc_rqst *rqstp, __be32 *p, struct svc_fh *fhp, struct kstat *stat) { *p++ = htonl(nfs3_ftypes[(stat->mode & S_IFMT) >> 12]); - *p++ = htonl((u32) stat->mode); + *p++ = htonl((u32) (stat->mode & S_IALLUGO)); *p++ = htonl((u32) stat->nlink); *p++ = htonl((u32) from_kuid(&init_user_ns, stat->uid)); *p++ = htonl((u32) from_kgid(&init_user_ns, stat->gid)); |