From: "Darrick J. Wong" <djwong@kernel.org>
To: Dave Chinner <david@fromorbit.com>
Cc: linux-xfs@vger.kernel.org
Subject: Re: [PATCH 1/5] xfs: remove XFS_PREALLOC_SYNC
Date: Mon, 31 Jan 2022 15:40:43 -0800 [thread overview]
Message-ID: <20220131234043.GG8313@magnolia> (raw)
In-Reply-To: <20220131233920.784181-2-david@fromorbit.com>
On Tue, Feb 01, 2022 at 10:39:16AM +1100, Dave Chinner wrote:
> From: Dave Chinner <dchinner@redhat.com>
>
> Callers can acheive the same thing by calling xfs_log_force_inode()
> after making their modifications. There is no need for
> xfs_update_prealloc_flags() to do this.
>
> Signed-off-by: Dave Chinner <dchinner@redhat.com>
Looks good,
Reviewed-by: Darrick J. Wong <djwong@kernel.org>
--D
> ---
> fs/xfs/xfs_file.c | 13 +++++++------
> fs/xfs/xfs_inode.h | 3 +--
> fs/xfs/xfs_pnfs.c | 6 ++++--
> 3 files changed, 12 insertions(+), 10 deletions(-)
>
> diff --git a/fs/xfs/xfs_file.c b/fs/xfs/xfs_file.c
> index 22ad207bedf4..ed375b3d0614 100644
> --- a/fs/xfs/xfs_file.c
> +++ b/fs/xfs/xfs_file.c
> @@ -95,8 +95,6 @@ xfs_update_prealloc_flags(
> ip->i_diflags &= ~XFS_DIFLAG_PREALLOC;
>
> xfs_trans_log_inode(tp, ip, XFS_ILOG_CORE);
> - if (flags & XFS_PREALLOC_SYNC)
> - xfs_trans_set_sync(tp);
> return xfs_trans_commit(tp);
> }
>
> @@ -1057,9 +1055,6 @@ xfs_file_fallocate(
> }
> }
>
> - if (file->f_flags & O_DSYNC)
> - flags |= XFS_PREALLOC_SYNC;
> -
> error = xfs_update_prealloc_flags(ip, flags);
> if (error)
> goto out_unlock;
> @@ -1082,8 +1077,14 @@ xfs_file_fallocate(
> * leave shifted extents past EOF and hence losing access to
> * the data that is contained within them.
> */
> - if (do_file_insert)
> + if (do_file_insert) {
> error = xfs_insert_file_space(ip, offset, len);
> + if (error)
> + goto out_unlock;
> + }
> +
> + if (file->f_flags & O_DSYNC)
> + error = xfs_log_force_inode(ip);
>
> out_unlock:
> xfs_iunlock(ip, iolock);
> diff --git a/fs/xfs/xfs_inode.h b/fs/xfs/xfs_inode.h
> index c447bf04205a..3fc6d77f5be9 100644
> --- a/fs/xfs/xfs_inode.h
> +++ b/fs/xfs/xfs_inode.h
> @@ -465,8 +465,7 @@ xfs_itruncate_extents(
> enum xfs_prealloc_flags {
> XFS_PREALLOC_SET = (1 << 1),
> XFS_PREALLOC_CLEAR = (1 << 2),
> - XFS_PREALLOC_SYNC = (1 << 3),
> - XFS_PREALLOC_INVISIBLE = (1 << 4),
> + XFS_PREALLOC_INVISIBLE = (1 << 3),
> };
>
> int xfs_update_prealloc_flags(struct xfs_inode *ip,
> diff --git a/fs/xfs/xfs_pnfs.c b/fs/xfs/xfs_pnfs.c
> index d6334abbc0b3..ce6d66f20385 100644
> --- a/fs/xfs/xfs_pnfs.c
> +++ b/fs/xfs/xfs_pnfs.c
> @@ -164,10 +164,12 @@ xfs_fs_map_blocks(
> * that the blocks allocated and handed out to the client are
> * guaranteed to be present even after a server crash.
> */
> - error = xfs_update_prealloc_flags(ip,
> - XFS_PREALLOC_SET | XFS_PREALLOC_SYNC);
> + error = xfs_update_prealloc_flags(ip, XFS_PREALLOC_SET);
> + if (!error)
> + error = xfs_log_force_inode(ip);
> if (error)
> goto out_unlock;
> +
> } else {
> xfs_iunlock(ip, lock_flags);
> }
> --
> 2.33.0
>
next prev parent reply other threads:[~2022-01-31 23:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-31 23:39 [PATCH 0/5 v2] xfs: fallocate() vs xfs_update_prealloc_flags() Dave Chinner
2022-01-31 23:39 ` [PATCH 1/5] xfs: remove XFS_PREALLOC_SYNC Dave Chinner
2022-01-31 23:40 ` Darrick J. Wong [this message]
2022-01-31 23:39 ` [PATCH 2/5] xfs: fallocate() should call file_modified() Dave Chinner
2022-01-31 23:39 ` [PATCH 3/5] xfs: set prealloc flag in xfs_alloc_file_space() Dave Chinner
2022-01-31 23:39 ` [PATCH 4/5] xfs: move xfs_update_prealloc_flags() to xfs_pnfs.c Dave Chinner
2022-01-31 23:41 ` Darrick J. Wong
2022-01-31 23:39 ` [PATCH 5/5] xfs: ensure log flush at the end of a synchronous fallocate call Dave Chinner
-- strict thread matches above, loose matches on Subject: below --
2022-01-30 4:59 [PATCHSET v2 0/3] xfs: fix permission drop and flushing in fallocate Darrick J. Wong
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
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=20220131234043.GG8313@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