summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorShuxiao Zhang <zhangshuxiao@xiaomi.com>2017-04-06 22:30:29 +0800
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2017-04-08 12:13:11 +0200
commit97fbfef6bd597888485b653175fb846c6998b60c (patch)
tree09534fe3154dcb01769604e43c3a12a1b7191379
parenta6d361404d81a03107a3475876afc22e1b84d5de (diff)
downloadlwn-97fbfef6bd597888485b653175fb846c6998b60c.tar.gz
lwn-97fbfef6bd597888485b653175fb846c6998b60c.zip
staging: android: ashmem: lseek failed due to no FMODE_LSEEK.
vfs_llseek will check whether the file mode has FMODE_LSEEK, no return failure. But ashmem can be lseek, so add FMODE_LSEEK to ashmem file. Comment From Greg Hackmann: ashmem_llseek() passes the llseek() call through to the backing shmem file. 91360b02ab48 ("ashmem: use vfs_llseek()") changed this from directly calling the file's llseek() op into a VFS layer call. This also adds a check for the FMODE_LSEEK bit, so without that bit ashmem_llseek() now always fails with -ESPIPE. Fixes: 91360b02ab48 ("ashmem: use vfs_llseek()") Signed-off-by: Shuxiao Zhang <zhangshuxiao@xiaomi.com> Tested-by: Greg Hackmann <ghackmann@google.com> Cc: stable <stable@vger.kernel.org> # 3.18+ Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
-rw-r--r--drivers/staging/android/ashmem.c1
1 files changed, 1 insertions, 0 deletions
diff --git a/drivers/staging/android/ashmem.c b/drivers/staging/android/ashmem.c
index 7cbad0d45b9c..6ba270e0494d 100644
--- a/drivers/staging/android/ashmem.c
+++ b/drivers/staging/android/ashmem.c
@@ -409,6 +409,7 @@ static int ashmem_mmap(struct file *file, struct vm_area_struct *vma)
ret = PTR_ERR(vmfile);
goto out;
}
+ vmfile->f_mode |= FMODE_LSEEK;
asma->file = vmfile;
}
get_file(asma->file);