From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Andy Strohman <astroh@amazon.com>
Cc: stable@vger.kernel.org, dchinner@redhat.com
Subject: Re: [PATCH 5.4] xfs: flush for older, xfs specific ioctls
Date: Thu, 5 Nov 2020 18:07:05 -0800 [thread overview]
Message-ID: <20201106020705.GC7118@magnolia> (raw)
In-Reply-To: <20201105202850.20216-1-astroh@amazon.com>
On Thu, Nov 05, 2020 at 08:28:50PM +0000, Andy Strohman wrote:
> 837a6e7f5cdb ("fs: add generic UNRESVSP and ZERO_RANGE ioctl handlers") changed
> ioctls XFS_IOC_UNRESVSP XFS_IOC_UNRESVSP64 and XFS_IOC_ZERO_RANGE to be generic
> instead of xfs specific.
>
> Because of this change, 36f11775da75 ("xfs: properly serialise fallocate against
> AIO+DIO") needed adaptation, as 5.4 still uses the xfs specific ioctls.
>
> Without this, xfstests xfs/242 and xfs/290 fail. Both of these tests test
> XFS_IOC_ZERO_RANGE.
>
> Fixes: 36f11775da75 ("xfs: properly serialise fallocate against AIO+DIO")
>
> Tested-by: Andy Strohman <astroh@amazon.com>
> Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com>
Yeah, looks good to me,
Reviewed-by: Darrick J. Wong <darrick.wong@oracle.com>
--D
> ---
> fs/xfs/xfs_ioctl.c | 26 +++++++++++++++++++++++++-
> 1 file changed, 25 insertions(+), 1 deletion(-)
>
> diff --git a/fs/xfs/xfs_ioctl.c b/fs/xfs/xfs_ioctl.c
> index bf0435dbec43..b3021d9b34a5 100644
> --- a/fs/xfs/xfs_ioctl.c
> +++ b/fs/xfs/xfs_ioctl.c
> @@ -622,7 +622,6 @@ xfs_ioc_space(
> error = xfs_break_layouts(inode, &iolock, BREAK_UNMAP);
> if (error)
> goto out_unlock;
> - inode_dio_wait(inode);
>
> switch (bf->l_whence) {
> case 0: /*SEEK_SET*/
> @@ -668,6 +667,31 @@ xfs_ioc_space(
> goto out_unlock;
> }
>
> + /*
> + * Must wait for all AIO to complete before we continue as AIO can
> + * change the file size on completion without holding any locks we
> + * currently hold. We must do this first because AIO can update both
> + * the on disk and in memory inode sizes, and the operations that follow
> + * require the in-memory size to be fully up-to-date.
> + */
> + inode_dio_wait(inode);
> +
> + /*
> + * Now that AIO and DIO has drained we can flush and (if necessary)
> + * invalidate the cached range over the first operation we are about to
> + * run. We include zero range here because it starts with a hole punch
> + * over the target range.
> + */
> + switch (cmd) {
> + case XFS_IOC_ZERO_RANGE:
> + case XFS_IOC_UNRESVSP:
> + case XFS_IOC_UNRESVSP64:
> + error = xfs_flush_unmap_range(ip, bf->l_start, bf->l_len);
> + if (error)
> + goto out_unlock;
> + break;
> + }
> +
> switch (cmd) {
> case XFS_IOC_ZERO_RANGE:
> flags |= XFS_PREALLOC_SET;
> --
> 2.16.6
>
next prev parent reply other threads:[~2020-11-06 2:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-05 20:28 [PATCH 5.4] xfs: flush for older, xfs specific ioctls Andy Strohman
2020-11-06 2:07 ` Darrick J. Wong [this message]
2020-11-09 10:33 ` Greg KH
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=20201106020705.GC7118@magnolia \
--to=darrick.wong@oracle.com \
--cc=astroh@amazon.com \
--cc=dchinner@redhat.com \
--cc=stable@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