All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <djwong@kernel.org>
To: Christoph Hellwig <hch@lst.de>
Cc: Chandan Babu R <chandan.babu@oracle.com>, linux-xfs@vger.kernel.org
Subject: Re: [PATCH 6/6] xfs: fold xfs_ilock_for_write_fault into xfs_write_fault
Date: Thu, 20 Jun 2024 11:57:12 -0700	[thread overview]
Message-ID: <20240620185712.GD103034@frogsfrogsfrogs> (raw)
In-Reply-To: <20240619115426.332708-7-hch@lst.de>

On Wed, Jun 19, 2024 at 01:53:56PM +0200, Christoph Hellwig wrote:
> Now that the page fault handler has been refactored, the only caller
> of xfs_ilock_for_write_fault is simple enough and calls it
> unconditionally.  Fold the logic and expand the comments explaining it.
> 
> Signed-off-by: Christoph Hellwig <hch@lst.de>

Makes sense to me,
Reviewed-by: Darrick J. Wong <djwong@kernel.org>

--D

> ---
>  fs/xfs/xfs_file.c | 33 +++++++++++++++------------------
>  1 file changed, 15 insertions(+), 18 deletions(-)
> 
> diff --git a/fs/xfs/xfs_file.c b/fs/xfs/xfs_file.c
> index 62a69ed796f2fd..05ea96661c475f 100644
> --- a/fs/xfs/xfs_file.c
> +++ b/fs/xfs/xfs_file.c
> @@ -227,21 +227,6 @@ xfs_ilock_iocb_for_write(
>  	return 0;
>  }
>  
> -static unsigned int
> -xfs_ilock_for_write_fault(
> -	struct xfs_inode	*ip)
> -{
> -	/* get a shared lock if no remapping in progress */
> -	xfs_ilock(ip, XFS_MMAPLOCK_SHARED);
> -	if (!xfs_iflags_test(ip, XFS_IREMAPPING))
> -		return XFS_MMAPLOCK_SHARED;
> -
> -	/* wait for remapping to complete */
> -	xfs_iunlock(ip, XFS_MMAPLOCK_SHARED);
> -	xfs_ilock(ip, XFS_MMAPLOCK_EXCL);
> -	return XFS_MMAPLOCK_EXCL;
> -}
> -
>  STATIC ssize_t
>  xfs_file_dio_read(
>  	struct kiocb		*iocb,
> @@ -1294,18 +1279,30 @@ xfs_write_fault(
>  	unsigned int		order)
>  {
>  	struct inode		*inode = file_inode(vmf->vma->vm_file);
> -	unsigned int		lock_mode;
> +	struct xfs_inode	*ip = XFS_I(inode);
> +	unsigned int		lock_mode = XFS_MMAPLOCK_SHARED;
>  	vm_fault_t		ret;
>  
>  	sb_start_pagefault(inode->i_sb);
>  	file_update_time(vmf->vma->vm_file);
>  
> -	lock_mode = xfs_ilock_for_write_fault(XFS_I(inode));
> +	/*
> +	 * Normally we only need the shared mmaplock, but if a reflink remap is
> +	 * in progress we take the exclusive lock to wait for the remap to
> +	 * finish before taking a write fault.
> +	 */
> +	xfs_ilock(ip, XFS_MMAPLOCK_SHARED);
> +	if (xfs_iflags_test(ip, XFS_IREMAPPING)) {
> +		xfs_iunlock(ip, XFS_MMAPLOCK_SHARED);
> +		xfs_ilock(ip, XFS_MMAPLOCK_EXCL);
> +		lock_mode = XFS_MMAPLOCK_EXCL;
> +	}
> +
>  	if (IS_DAX(inode))
>  		ret = xfs_dax_fault_locked(vmf, order, true);
>  	else
>  		ret = iomap_page_mkwrite(vmf, &xfs_page_mkwrite_iomap_ops);
> -	xfs_iunlock(XFS_I(inode), lock_mode);
> +	xfs_iunlock(ip, lock_mode);
>  
>  	sb_end_pagefault(inode->i_sb);
>  	return ret;
> -- 
> 2.43.0
> 
> 

  reply	other threads:[~2024-06-20 18:57 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-19 11:53 clean up I/O path inode locking helpers and the page fault handler Christoph Hellwig
2024-06-19 11:53 ` [PATCH 1/6] xfs: move the dio write relocking out of xfs_ilock_for_iomap Christoph Hellwig
2024-06-20 18:40   ` Darrick J. Wong
2024-06-19 11:53 ` [PATCH 2/6] xfs: cleanup xfs_ilock_iocb_for_write Christoph Hellwig
2024-06-20 18:41   ` Darrick J. Wong
2024-06-19 11:53 ` [PATCH 3/6] xfs: simplify xfs_dax_fault Christoph Hellwig
2024-06-20 18:50   ` Darrick J. Wong
2024-06-21  5:05     ` Christoph Hellwig
2024-06-21 17:43       ` Darrick J. Wong
2024-06-19 11:53 ` [PATCH 4/6] xfs: refactor __xfs_filemap_fault Christoph Hellwig
2024-06-20 18:54   ` Darrick J. Wong
2024-06-21  5:08     ` Christoph Hellwig
2024-06-19 11:53 ` [PATCH 5/6] xfs: always take XFS_MMAPLOCK shared in xfs_dax_fault Christoph Hellwig
2024-06-20 18:56   ` Darrick J. Wong
2024-06-19 11:53 ` [PATCH 6/6] xfs: fold xfs_ilock_for_write_fault into xfs_write_fault Christoph Hellwig
2024-06-20 18:57   ` Darrick J. Wong [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-06-23  5:44 clean up I/O path inode locking helpers and the page fault handler v2 Christoph Hellwig
2024-06-23  5:44 ` [PATCH 6/6] xfs: fold xfs_ilock_for_write_fault into xfs_write_fault 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=20240620185712.GD103034@frogsfrogsfrogs \
    --to=djwong@kernel.org \
    --cc=chandan.babu@oracle.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.