From: "Darrick J. Wong" <djwong@kernel.org>
To: Dave Chinner <david@fromorbit.com>
Cc: linux-xfs@vger.kernel.org
Subject: Re: [PATCH 5/5] xfs: ensure log flush at the end of a synchronous fallocate call
Date: Tue, 1 Feb 2022 08:37:08 -0800 [thread overview]
Message-ID: <20220201163708.GI8313@magnolia> (raw)
In-Reply-To: <20220131064350.739863-6-david@fromorbit.com>
On Mon, Jan 31, 2022 at 05:43:50PM +1100, Dave Chinner wrote:
> From: "Darrick J. Wong" <djwong@kernel.org>
>
> Since we've started treating fallocate more like a file write, we
> should flush the log to disk if the user has asked for synchronous
> writes either by setting it via fcntl flags, or inode flags, or with
> the sync mount option. We've already got a helper for this, so use
> it.
>
> [Slightly massaged by <dchinner@redhat.com> to fit this patchset]
I think you made more than 'slight massage' changes...
> Signed-off-by: Darrick J. Wong <djwong@kernel.org>
> Signed-off-by: Dave Chinner <dchinner@redhat.com>
> ---
> fs/xfs/xfs_file.c | 32 ++++++++++++++++----------------
> 1 file changed, 16 insertions(+), 16 deletions(-)
>
> diff --git a/fs/xfs/xfs_file.c b/fs/xfs/xfs_file.c
> index ddc3336e8f84..209cba0f0ddc 100644
> --- a/fs/xfs/xfs_file.c
> +++ b/fs/xfs/xfs_file.c
> @@ -861,6 +861,21 @@ xfs_break_layouts(
> return error;
> }
>
> +/* Does this file, inode, or mount want synchronous writes? */
> +static inline bool xfs_file_sync_writes(struct file *filp)
> +{
> + struct xfs_inode *ip = XFS_I(file_inode(filp));
> +
> + if (xfs_has_wsync(ip->i_mount))
> + return true;
> + if (filp->f_flags & (__O_SYNC | O_DSYNC))
> + return true;
> + if (IS_SYNC(file_inode(filp)))
> + return true;
> +
> + return false;
> +}
> +
> #define XFS_FALLOC_FL_SUPPORTED \
> (FALLOC_FL_KEEP_SIZE | FALLOC_FL_PUNCH_HOLE | \
> FALLOC_FL_COLLAPSE_RANGE | FALLOC_FL_ZERO_RANGE | \
> @@ -1045,7 +1060,7 @@ xfs_file_fallocate(
> if (do_file_insert)
> error = xfs_insert_file_space(ip, offset, len);
>
> - if (file->f_flags & O_DSYNC)
> + if (xfs_file_sync_writes(file))
> error = xfs_log_force_inode(ip);
...since the preceeding patches that you wrote enable simpler logic
here. You've done all the (re)thinking necessary to get here, so I
think on those grounds:
Reviewed-by: Darrick J. Wong <djwong@kernel.org>
--D
>
> out_unlock:
> @@ -1078,21 +1093,6 @@ xfs_file_fadvise(
> return ret;
> }
>
> -/* Does this file, inode, or mount want synchronous writes? */
> -static inline bool xfs_file_sync_writes(struct file *filp)
> -{
> - struct xfs_inode *ip = XFS_I(file_inode(filp));
> -
> - if (xfs_has_wsync(ip->i_mount))
> - return true;
> - if (filp->f_flags & (__O_SYNC | O_DSYNC))
> - return true;
> - if (IS_SYNC(file_inode(filp)))
> - return true;
> -
> - return false;
> -}
> -
> STATIC loff_t
> xfs_file_remap_range(
> struct file *file_in,
> --
> 2.33.0
>
next prev parent reply other threads:[~2022-02-01 16:37 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-30 4:59 [PATCHSET v2 0/3] xfs: fix permission drop and flushing in fallocate Darrick J. Wong
2022-01-30 4:59 ` [PATCH 1/3] xfs: use vfs helper to update file attributes after fallocate Darrick J. Wong
2022-01-30 22:30 ` Dave Chinner
2022-01-30 4:59 ` [PATCH 2/3] xfs: flush log after fallocate for sync mounts and sync inodes Darrick J. Wong
2022-01-30 4:59 ` [PATCH 3/3] xfs: ensure log flush at the end of a synchronous fallocate call Darrick J. Wong
2022-01-30 21:59 ` Dave Chinner
2022-01-31 6:43 ` [PATCH 0/5] xfs: fallocate() vs xfs_update_prealloc_flags() Dave Chinner
2022-01-31 6:43 ` [PATCH 1/5] xfs: remove XFS_PREALLOC_SYNC Dave Chinner
2022-01-31 17:25 ` Darrick J. Wong
2022-01-31 6:43 ` [PATCH 2/5] xfs: fallocate() should call file_modified() Dave Chinner
2022-01-31 17:27 ` Darrick J. Wong
2022-01-31 6:43 ` [PATCH 3/5] xfs: set prealloc flag in xfs_alloc_file_space() Dave Chinner
2022-01-31 7:02 ` [PATCH v1.1 " Dave Chinner
2022-01-31 17:30 ` Darrick J. Wong
2022-01-31 6:43 ` [PATCH 4/5] xfs: move xfs_update_prealloc_flags() to xfs_pnfs.c Dave Chinner
2022-01-31 17:37 ` Darrick J. Wong
2022-01-31 6:43 ` [PATCH 5/5] xfs: ensure log flush at the end of a synchronous fallocate call Dave Chinner
2022-02-01 16:37 ` Darrick J. Wong [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-01-31 23:39 [PATCH 0/5 v2] xfs: fallocate() vs xfs_update_prealloc_flags() Dave Chinner
2022-01-31 23:39 ` [PATCH 5/5] xfs: ensure log flush at the end of a synchronous fallocate call Dave Chinner
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=20220201163708.GI8313@magnolia \
--to=djwong@kernel.org \
--cc=david@fromorbit.com \
--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