summaryrefslogtreecommitdiffstats
path: root/fs/nfs/nfs4proc.c
diff options
context:
space:
mode:
authorChuck Lever <chuck.lever@oracle.com>2015-05-06 18:26:58 -0400
committerTrond Myklebust <trond.myklebust@primarydata.com>2015-05-13 14:56:03 -0400
commit6b19687563fa6f385ac314afa30b7579e8c3174c (patch)
treea7cd752f3ec84a8a10545071d409d92c080cb77e /fs/nfs/nfs4proc.c
parent030bbdbf4c833bc69f502eae58498bc5572db736 (diff)
downloadop-kernel-dev-6b19687563fa6f385ac314afa30b7579e8c3174c.zip
op-kernel-dev-6b19687563fa6f385ac314afa30b7579e8c3174c.tar.gz
nfs: stat(2) fails during cthon04 basic test5 on NFSv4.0
When running the Connectathon basic tests against a Solaris NFS server over NFSv4.0, test5 reports that stat(2) returns a file size of zero instead of 1MB. On success, nfs_commit_inode() can return a positive result; see other call sites such as nfs_file_fsync_commit() and nfs_commit_unstable_pages(). The call site recently added in nfs_wb_all() does not prevent that positive return value from leaking to its callers. If it leaks through nfs_sync_inode() back to nfs_getattr(), that causes stat(2) to return a positive return value to user space while also not filling in the passed-in struct stat. Additional clean up: the new logic in nfs_wb_all() is rewritten in bfields-normal form. Fixes: 5bb89b4702e2 ("NFSv4.1/pnfs: Separate out metadata . . .") Signed-off-by: Chuck Lever <chuck.lever@oracle.com> Signed-off-by: Trond Myklebust <trond.myklebust@primarydata.com>
Diffstat (limited to 'fs/nfs/nfs4proc.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud