From: Damien Le Moal <dlemoal@kernel.org>
To: David Howells <dhowells@redhat.com>, Jens Axboe <axboe@kernel.dk>,
Al Viro <viro@zeniv.linux.org.uk>,
Christoph Hellwig <hch@infradead.org>
Cc: Matthew Wilcox <willy@infradead.org>, Jan Kara <jack@suse.cz>,
Jeff Layton <jlayton@kernel.org>,
David Hildenbrand <david@redhat.com>,
Jason Gunthorpe <jgg@nvidia.com>,
Logan Gunthorpe <logang@deltatee.com>,
Hillf Danton <hdanton@sina.com>,
Christian Brauner <brauner@kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-fsdevel@vger.kernel.org, linux-block@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Christoph Hellwig <hch@lst.de>,
"Darrick J . Wong" <djwong@kernel.org>,
linux-xfs@vger.kernel.org
Subject: Re: [PATCH v22 25/31] zonefs: Provide a splice-read wrapper
Date: Tue, 23 May 2023 11:48:17 +0900 [thread overview]
Message-ID: <12153db1-20af-040b-ded0-31286b5bafca@kernel.org> (raw)
In-Reply-To: <20230522135018.2742245-26-dhowells@redhat.com>
On 5/22/23 22:50, David Howells wrote:
> Provide a splice_read wrapper for zonefs. This does some checks before
> proceeding and locks the inode across the call to filemap_splice_read() and
> a size check in case of truncation. Splicing from direct I/O is handled by
> the caller.
>
> Signed-off-by: David Howells <dhowells@redhat.com>
> cc: Christoph Hellwig <hch@lst.de>
> cc: Al Viro <viro@zeniv.linux.org.uk>
> cc: Jens Axboe <axboe@kernel.dk>
> cc: Darrick J. Wong <djwong@kernel.org>
> cc: linux-xfs@vger.kernel.org
> cc: linux-fsdevel@vger.kernel.org
> cc: linux-block@vger.kernel.org
> cc: linux-mm@kvack.org
One comment below but otherwise looks OK.
Acked-by: Damien Le Moal <dlemoal@kernel.org>
> ---
> fs/zonefs/file.c | 40 +++++++++++++++++++++++++++++++++++++++-
> 1 file changed, 39 insertions(+), 1 deletion(-)
>
> diff --git a/fs/zonefs/file.c b/fs/zonefs/file.c
> index 132f01d3461f..65d4c4fe6364 100644
> --- a/fs/zonefs/file.c
> +++ b/fs/zonefs/file.c
> @@ -752,6 +752,44 @@ static ssize_t zonefs_file_read_iter(struct kiocb *iocb, struct iov_iter *to)
> return ret;
> }
>
> +static ssize_t zonefs_file_splice_read(struct file *in, loff_t *ppos,
> + struct pipe_inode_info *pipe,
> + size_t len, unsigned int flags)
> +{
> + struct inode *inode = file_inode(in);
> + struct zonefs_inode_info *zi = ZONEFS_I(inode);
> + struct zonefs_zone *z = zonefs_inode_zone(inode);
> + loff_t isize;
> + ssize_t ret = 0;
> +
> + /* Offline zones cannot be read */
> + if (unlikely(IS_IMMUTABLE(inode) && !(inode->i_mode & 0777)))
> + return -EPERM;
> +
> + if (*ppos >= z->z_capacity)
> + return 0;
> +
> + inode_lock_shared(inode);
> +
> + /* Limit read operations to written data */
> + mutex_lock(&zi->i_truncate_mutex);
> + isize = i_size_read(inode);
> + if (*ppos >= isize)
> + len = 0;
> + else
> + len = min_t(loff_t, len, isize - *ppos);
> + mutex_unlock(&zi->i_truncate_mutex);
> +
> + if (len > 0) {
> + ret = filemap_splice_read(in, ppos, pipe, len, flags);
> + if (ret == -EIO)
Is -EIO the only error that filemap_splice_read() may return ? There are other
IO error codes that we could get from the block layer, e.g. -ETIMEDOUT etc. So
"if (ret < 0)" may be better here ?
> + zonefs_io_error(inode, false);
> + }
> +
> + inode_unlock_shared(inode);
> + return ret;
> +}
> +
> /*
> * Write open accounting is done only for sequential files.
> */
> @@ -896,7 +934,7 @@ const struct file_operations zonefs_file_operations = {
> .llseek = zonefs_file_llseek,
> .read_iter = zonefs_file_read_iter,
> .write_iter = zonefs_file_write_iter,
> - .splice_read = generic_file_splice_read,
> + .splice_read = zonefs_file_splice_read,
> .splice_write = iter_file_splice_write,
> .iopoll = iocb_bio_iopoll,
> };
>
--
Damien Le Moal
Western Digital Research
next prev parent reply other threads:[~2023-05-23 2:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230522135018.2742245-1-dhowells@redhat.com>
2023-05-22 13:49 ` [PATCH v22 08/31] splice: Make splice from a DAX file use copy_splice_read() David Howells
2023-05-22 13:50 ` [PATCH v22 24/31] xfs: Provide a splice-read wrapper David Howells
2023-05-22 13:50 ` [PATCH v22 25/31] zonefs: " David Howells
2023-05-23 2:48 ` Damien Le Moal [this message]
2023-05-23 20:43 ` David Howells
2023-05-24 23:13 ` Damien Le Moal
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=12153db1-20af-040b-ded0-31286b5bafca@kernel.org \
--to=dlemoal@kernel.org \
--cc=axboe@kernel.dk \
--cc=brauner@kernel.org \
--cc=david@redhat.com \
--cc=dhowells@redhat.com \
--cc=djwong@kernel.org \
--cc=hch@infradead.org \
--cc=hch@lst.de \
--cc=hdanton@sina.com \
--cc=jack@suse.cz \
--cc=jgg@nvidia.com \
--cc=jlayton@kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-xfs@vger.kernel.org \
--cc=logang@deltatee.com \
--cc=torvalds@linux-foundation.org \
--cc=viro@zeniv.linux.org.uk \
--cc=willy@infradead.org \
/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