public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Damien Le Moal <dlemoal@kernel.org>
To: cem@kernel.org, linux-xfs@vger.kernel.org
Cc: hch@lst.de
Subject: Re: [PATCH 2/4] xfs: move zoned dio ioend to its own function
Date: Tue, 10 Mar 2026 13:54:26 +0100	[thread overview]
Message-ID: <024f90cd-2bfc-4ef7-aa4f-8808bd601e89@kernel.org> (raw)
In-Reply-To: <20260310115555.114197-3-cem@kernel.org>

On 2026/03/10 12:55, cem@kernel.org wrote:
> From: Carlos Maiolino <cem@kernel.org>
> 
> All zoned dio needs during endio is set the file size, so move it
> out of the generic function.

"move" is unclear here since this patch is adding code but not deleting
anything. Maye be rephrase this ?

> 
> Signed-off-by: Carlos Maiolino <cmaiolino@redhat.com>
> ---
>  fs/xfs/xfs_file.c | 35 ++++++++++++++++++++++++++++++++---
>  1 file changed, 32 insertions(+), 3 deletions(-)
> 
> diff --git a/fs/xfs/xfs_file.c b/fs/xfs/xfs_file.c
> index 45ecd743fa32..29b02673111b 100644
> --- a/fs/xfs/xfs_file.c
> +++ b/fs/xfs/xfs_file.c
> @@ -595,6 +595,36 @@ xfs_dio_endio_set_isize(
>  	return xfs_setfilesize(ip, offset, size);
>  }
>  
> +static int
> +xfs_zoned_dio_write_end_io(
> +	struct kiocb		*iocb,
> +	ssize_t			size,
> +	int			error,
> +	unsigned		flags)
> +{
> +	struct inode		*inode = file_inode(iocb->ki_filp);
> +	struct xfs_inode	*ip = XFS_I(inode);
> +	unsigned int		nofs_flag;
> +
> +	ASSERT(!(flags & (IOMAP_DIO_UNWRITTEN | IOMAP_DIO_COW)));
> +
> +	trace_xfs_end_io_direct_write(ip, iocb->ki_pos, size);
> +
> +	if (xfs_is_shutdown(ip->i_mount))
> +		return -EIO;
> +
> +	if (error || !size)
> +		return error;
> +
> +	XFS_STATS_ADD(ip->i_mount, xs_write_bytes, size);
> +
> +	nofs_flag = memalloc_nofs_save();
> +	error = xfs_dio_endio_set_isize(inode, iocb->ki_pos, size);
> +	memalloc_nofs_restore(nofs_flag);
> +
> +	return error;
> +}
> +
>  static int
>  xfs_dio_write_end_io(
>  	struct kiocb		*iocb,
> @@ -607,8 +637,7 @@ xfs_dio_write_end_io(
>  	loff_t			offset = iocb->ki_pos;
>  	unsigned int		nofs_flag;
>  
> -	ASSERT(!xfs_is_zoned_inode(ip) ||
> -	       !(flags & (IOMAP_DIO_UNWRITTEN | IOMAP_DIO_COW)));
> +	ASSERT(!xfs_is_zoned_inode(ip));
>  
>  	trace_xfs_end_io_direct_write(ip, offset, size);
>  
> @@ -701,7 +730,7 @@ xfs_dio_zoned_submit_io(
>  static const struct iomap_dio_ops xfs_dio_zoned_write_ops = {
>  	.bio_set	= &iomap_ioend_bioset,
>  	.submit_io	= xfs_dio_zoned_submit_io,
> -	.end_io		= xfs_dio_write_end_io,
> +	.end_io		= xfs_zoned_dio_write_end_io,
>  };
>  
>  /*


-- 
Damien Le Moal
Western Digital Research

  parent reply	other threads:[~2026-03-10 12:54 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-10 11:55 [PATCH 0/4] Zoned device cleanups cem
2026-03-10 11:55 ` [PATCH 1/4] xfs: factor out isize updates from xfs_dio_write_end_io cem
2026-03-10 12:51   ` Damien Le Moal
2026-03-10 12:52   ` Christoph Hellwig
2026-03-10 11:55 ` [PATCH 2/4] xfs: move zoned dio ioend to its own function cem
2026-03-10 12:53   ` Christoph Hellwig
2026-03-10 12:54   ` Damien Le Moal [this message]
2026-03-10 11:55 ` [PATCH 3/4] xfs: factor out xfs_zone_inc_written cem
2026-03-10 12:54   ` Christoph Hellwig
2026-03-10 12:55   ` Damien Le Moal
2026-03-10 11:55 ` [PATCH 4/4] xfs: opencode xfs_zone_record_blocks cem
2026-03-10 12:54   ` Christoph Hellwig
2026-03-10 12:56   ` 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=024f90cd-2bfc-4ef7-aa4f-8808bd601e89@kernel.org \
    --to=dlemoal@kernel.org \
    --cc=cem@kernel.org \
    --cc=hch@lst.de \
    --cc=linux-xfs@vger.kernel.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