From: Christoph Hellwig <hch@lst.de>
To: viro@zeniv.linux.org.uk
Cc: arve@android.com, riandrews@android.com,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 01/17] ashmem: switch to ->read_iter
Date: Fri, 1 Sep 2017 17:39:09 +0200 [thread overview]
Message-ID: <20170901153925.30578-2-hch@lst.de> (raw)
In-Reply-To: <20170901153925.30578-1-hch@lst.de>
And use the proper VFS helper for using the backing file.
Also make sure we hold ashmem_lock while updating f_pos to make sure that
it's not racy.
Signed-off-by: Christoph Hellwig <hch@lst.de>
---
drivers/staging/android/ashmem.c | 29 ++++++++---------------------
1 file changed, 8 insertions(+), 21 deletions(-)
diff --git a/drivers/staging/android/ashmem.c b/drivers/staging/android/ashmem.c
index 6ba270e0494d..0f695df14c9d 100644
--- a/drivers/staging/android/ashmem.c
+++ b/drivers/staging/android/ashmem.c
@@ -294,19 +294,9 @@ static int ashmem_release(struct inode *ignored, struct file *file)
return 0;
}
-/**
- * ashmem_read() - Reads a set of bytes from an Ashmem-enabled file
- * @file: The associated backing file.
- * @buf: The buffer of data being written to
- * @len: The number of bytes being read
- * @pos: The position of the first byte to read.
- *
- * Return: 0 if successful, or another return code if not.
- */
-static ssize_t ashmem_read(struct file *file, char __user *buf,
- size_t len, loff_t *pos)
+static ssize_t ashmem_read_iter(struct kiocb *iocb, struct iov_iter *iter)
{
- struct ashmem_area *asma = file->private_data;
+ struct ashmem_area *asma = iocb->ki_filp->private_data;
int ret = 0;
mutex_lock(&ashmem_mutex);
@@ -320,20 +310,17 @@ static ssize_t ashmem_read(struct file *file, char __user *buf,
goto out_unlock;
}
- mutex_unlock(&ashmem_mutex);
-
/*
* asma and asma->file are used outside the lock here. We assume
* once asma->file is set it will never be changed, and will not
* be destroyed until all references to the file are dropped and
* ashmem_release is called.
*/
- ret = __vfs_read(asma->file, buf, len, pos);
- if (ret >= 0)
- /** Update backing file pos, since f_ops->read() doesn't */
- asma->file->f_pos = *pos;
- return ret;
-
+ mutex_unlock(&ashmem_mutex);
+ ret = vfs_iter_read(asma->file, iter, &iocb->ki_pos, 0);
+ mutex_lock(&ashmem_mutex);
+ if (ret > 0)
+ asma->file->f_pos = iocb->ki_pos;
out_unlock:
mutex_unlock(&ashmem_mutex);
return ret;
@@ -834,7 +821,7 @@ static const struct file_operations ashmem_fops = {
.owner = THIS_MODULE,
.open = ashmem_open,
.release = ashmem_release,
- .read = ashmem_read,
+ .read_iter = ashmem_read_iter,
.llseek = ashmem_llseek,
.mmap = ashmem_mmap,
.unlocked_ioctl = ashmem_ioctl,
--
2.11.0
next prev parent reply other threads:[~2017-09-01 15:39 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-01 15:39 switch in-kernel read/write calls to kernel_read/write V2 Christoph Hellwig
2017-09-01 15:39 ` Christoph Hellwig [this message]
2017-09-01 15:39 ` [PATCH 02/17] autofs4: switch autofs4_write to __kernel_write Christoph Hellwig
2017-09-01 15:39 ` [PATCH 03/17] fs: move kernel_write to fs/read_write.c Christoph Hellwig
2017-09-01 15:39 ` [PATCH 04/17] fs: move kernel_read " Christoph Hellwig
2017-09-01 15:39 ` [PATCH 05/17] fs: fix kernel_read prototype Christoph Hellwig
2017-09-01 15:39 ` [PATCH 06/17] fs: fix kernel_write prototype Christoph Hellwig
2017-09-01 15:39 ` [PATCH 07/17] fs: make the buf argument to __kernel_write a void pointer Christoph Hellwig
2017-09-01 15:39 ` [PATCH 08/17] serial2002: switch serial2002_tty_write to kernel_{read/write} Christoph Hellwig
2017-09-01 15:39 ` [PATCH 09/17] mm/nommu: switch do_mmap_private to kernel_read Christoph Hellwig
2017-09-01 15:39 ` [PATCH 10/17] net/9p: switch p9_fd_read to kernel_write Christoph Hellwig
2017-09-01 15:39 ` [PATCH 11/17] btrfs: switch write_buf " Christoph Hellwig
2017-09-01 15:39 ` [PATCH 12/17] mconsole: switch to kernel_read Christoph Hellwig
2017-09-01 15:39 ` [PATCH 13/17] gadget/f_mass_storage: stop messing with the address limit Christoph Hellwig
2017-09-01 15:39 ` [PATCH 14/17] lustre: switch to kernel_write Christoph Hellwig
2017-09-01 15:39 ` [PATCH 15/17] fs: unexport __vfs_read/__vfs_write Christoph Hellwig
2017-09-01 15:39 ` [PATCH 16/17] fs: unexport vfs_read and vfs_write Christoph Hellwig
2017-09-01 15:39 ` [PATCH 17/17] fs: unexport vfs_readv and vfs_writev Christoph Hellwig
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170901153925.30578-2-hch@lst.de \
--to=hch@lst.de \
--cc=arve@android.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=riandrews@android.com \
--cc=viro@zeniv.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).