cifs: fix revalidation test in cifs_llseek()
This test is always true so it means we revalidate the length every time, which generates more network traffic. When it is SEEK_SET or SEEK_CUR, then we don't need to revalidate. Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com> Reviewed-by: Jeff Layton <jlayton@redhat.com> Signed-off-by: Steve French <sfrench@us.ibm.com>
This commit is contained in:
parent
7ee94d97aa
commit
48a5730e5b
1 changed files with 1 additions and 1 deletions
|
@ -699,7 +699,7 @@ static loff_t cifs_llseek(struct file *file, loff_t offset, int origin)
|
||||||
* origin == SEEK_END || SEEK_DATA || SEEK_HOLE => we must revalidate
|
* origin == SEEK_END || SEEK_DATA || SEEK_HOLE => we must revalidate
|
||||||
* the cached file length
|
* the cached file length
|
||||||
*/
|
*/
|
||||||
if (origin != SEEK_SET || origin != SEEK_CUR) {
|
if (origin != SEEK_SET && origin != SEEK_CUR) {
|
||||||
int rc;
|
int rc;
|
||||||
struct inode *inode = file->f_path.dentry->d_inode;
|
struct inode *inode = file->f_path.dentry->d_inode;
|
||||||
|
|
||||||
|
|
Loading…
Reference in a new issue