NFSv4.2 fix handling of sr_eof in SEEK's reply
Currently the client ignores the value of the sr_eof of the SEEK operation. According to the spec, if the server didn't find the requested extent and reached the end of the file, the server would return sr_eof=true. In case the request for DATA and no data was found (ie in the middle of the hole), then the lseek expects that ENXIO would be returned. Fixes: 1c6dcbe5ceff8 ("NFS: Implement SEEK") Signed-off-by: Olga Kornievskaia <kolga@netapp.com> Signed-off-by: Trond Myklebust <trond.myklebust@hammerspace.com>
This commit is contained in:
parent
ed34695e15
commit
73f5c88f52
@ -667,7 +667,10 @@ static loff_t _nfs42_proc_llseek(struct file *filep,
|
||||
if (status)
|
||||
return status;
|
||||
|
||||
return vfs_setpos(filep, res.sr_offset, inode->i_sb->s_maxbytes);
|
||||
if (whence == SEEK_DATA && res.sr_eof)
|
||||
return -NFS4ERR_NXIO;
|
||||
else
|
||||
return vfs_setpos(filep, res.sr_offset, inode->i_sb->s_maxbytes);
|
||||
}
|
||||
|
||||
loff_t nfs42_proc_llseek(struct file *filep, loff_t offset, int whence)
|
||||
|
Loading…
x
Reference in New Issue
Block a user