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 3/6] xfs: simplify xfs_dax_fault
Date: Thu, 20 Jun 2024 11:50:26 -0700 [thread overview]
Message-ID: <20240620185026.GA103034@frogsfrogsfrogs> (raw)
In-Reply-To: <20240619115426.332708-4-hch@lst.de>
On Wed, Jun 19, 2024 at 01:53:53PM +0200, Christoph Hellwig wrote:
> Replace the separate stub with an IS_ENABLED check, and take the call to
> dax_finish_sync_fault into xfs_dax_fault instead of leaving it in the
> caller.
>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
> ---
> fs/xfs/xfs_file.c | 34 +++++++++++++---------------------
> 1 file changed, 13 insertions(+), 21 deletions(-)
>
> diff --git a/fs/xfs/xfs_file.c b/fs/xfs/xfs_file.c
> index 74c2c8d253e69b..8aab2f66fe016f 100644
> --- a/fs/xfs/xfs_file.c
> +++ b/fs/xfs/xfs_file.c
> @@ -1251,31 +1251,27 @@ xfs_file_llseek(
> return vfs_setpos(file, offset, inode->i_sb->s_maxbytes);
> }
>
> -#ifdef CONFIG_FS_DAX
> static inline vm_fault_t
> xfs_dax_fault(
> struct vm_fault *vmf,
> unsigned int order,
> - bool write_fault,
> - pfn_t *pfn)
> + bool write_fault)
> {
> - return dax_iomap_fault(vmf, order, pfn, NULL,
> + vm_fault_t ret;
> + pfn_t pfn;
> +
> + if (!IS_ENABLED(CONFIG_FS_DAX)) {
> + ASSERT(0);
> + return VM_FAULT_SIGBUS;
Does this actually work if FS_DAX=n? AFAICT there's no !DAX stub for
dax_iomap_fault, so won't that cause a linker error?
> + }
> + ret = dax_iomap_fault(vmf, order, &pfn, NULL,
> (write_fault && !vmf->cow_page) ?
> &xfs_dax_write_iomap_ops :
> &xfs_read_iomap_ops);
> + if (ret & VM_FAULT_NEEDDSYNC)
> + ret = dax_finish_sync_fault(vmf, order, pfn);
> + return ret;
I /almost/ wondered if these ought to be separate helpers for read and
write faults, but then I realized the (write && cow_page) case is a
"read" and ... lol. So the only question I have is about linker errors.
--D
> }
> -#else
> -static inline vm_fault_t
> -xfs_dax_fault(
> - struct vm_fault *vmf,
> - unsigned int order,
> - bool write_fault,
> - pfn_t *pfn)
> -{
> - ASSERT(0);
> - return VM_FAULT_SIGBUS;
> -}
> -#endif
>
> /*
> * Locking for serialisation of IO during page faults. This results in a lock
> @@ -1309,11 +1305,7 @@ __xfs_filemap_fault(
> lock_mode = xfs_ilock_for_write_fault(XFS_I(inode));
>
> if (IS_DAX(inode)) {
> - pfn_t pfn;
> -
> - ret = xfs_dax_fault(vmf, order, write_fault, &pfn);
> - if (ret & VM_FAULT_NEEDDSYNC)
> - ret = dax_finish_sync_fault(vmf, order, pfn);
> + ret = xfs_dax_fault(vmf, order, write_fault);
> } else if (write_fault) {
> ret = iomap_page_mkwrite(vmf, &xfs_page_mkwrite_iomap_ops);
> } else {
> --
> 2.43.0
>
>
next prev parent reply other threads:[~2024-06-20 18:50 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 [this message]
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
-- 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 3/6] xfs: simplify xfs_dax_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=20240620185026.GA103034@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox