From: Zorro Lang <zlang@redhat.com>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: guaneryu@gmail.com, linux-xfs@vger.kernel.org,
fstests@vger.kernel.org, guan@eryu.me, amir73il@gmail.com
Subject: Re: [PATCH 1/2] xfs: make sure syncfs(2) passes back super_operations.sync_fs errors
Date: Wed, 20 Apr 2022 03:10:14 +0800 [thread overview]
Message-ID: <20220419191014.ebcfzdbtg45fhg27@zlang-mailbox> (raw)
In-Reply-To: <165038953550.1677711.12931148474635467556.stgit@magnolia>
On Tue, Apr 19, 2022 at 10:32:15AM -0700, Darrick J. Wong wrote:
> From: Darrick J. Wong <djwong@kernel.org>
>
> This is a regression test to make sure that nonzero error returns from
> a filesystem's ->sync_fs implementation are actually passed back to
> userspace when the call stack involves syncfs(2).
>
> Signed-off-by: Darrick J. Wong <djwong@kernel.org>
> Reviewed-by: Zorro Lang <zlang@redhat.com>
> ---
> tests/xfs/839 | 42 ++++++++++++++++++++++++++++++++++++++++++
> tests/xfs/839.out | 2 ++
> 2 files changed, 44 insertions(+)
> create mode 100755 tests/xfs/839
> create mode 100644 tests/xfs/839.out
>
>
> diff --git a/tests/xfs/839 b/tests/xfs/839
> new file mode 100755
> index 00000000..9bfe93ef
> --- /dev/null
> +++ b/tests/xfs/839
> @@ -0,0 +1,42 @@
> +#! /bin/bash
> +# SPDX-License-Identifier: GPL-2.0
> +# Copyright (c) 2022 Oracle. All Rights Reserved.
> +#
> +# FS QA Test No. 839
> +#
> +# Regression test for kernel commits:
> +#
> +# 5679897eb104 ("vfs: make sync_filesystem return errors from ->sync_fs")
> +# 2d86293c7075 ("xfs: return errors in xfs_fs_sync_fs")
> +#
> +# During a code inspection, I noticed that sync_filesystem ignores the return
> +# value of the ->sync_fs calls that it makes. sync_filesystem, in turn is used
> +# by the syncfs(2) syscall to persist filesystem changes to disk. This means
> +# that syncfs(2) does not capture internal filesystem errors that are neither
> +# visible from the block device (e.g. media error) nor recorded in s_wb_err.
> +# XFS historically returned 0 from ->sync_fs even if there were log failures,
> +# so that had to be corrected as well.
> +#
> +# The kernel commits above fix this problem, so this test tries to trigger the
> +# bug by using the shutdown ioctl on a clean, freshly mounted filesystem in the
> +# hope that the EIO generated as a result of the filesystem being shut down is
> +# only visible via ->sync_fs.
> +#
> +. ./common/preamble
> +_begin_fstest auto quick shutdown
> +
> +# real QA test starts here
> +
> +# Modify as appropriate.
Good to me, we can help to add the missing "_supported_fs xfs", if you don't
like to send a new version for that again.
Reviewed-by: Zorro Lang <zlang@redhat.com>
> +_require_xfs_io_command syncfs
> +_require_scratch_nocheck
> +_require_scratch_shutdown
> +
> +# Reuse the fs formatted when we checked for the shutdown ioctl, and don't
> +# bother checking the filesystem afterwards since we never wrote anything.
> +_scratch_mount
> +$XFS_IO_PROG -x -c 'shutdown -f ' -c syncfs $SCRATCH_MNT
> +
> +# success, all done
> +status=0
> +exit
> diff --git a/tests/xfs/839.out b/tests/xfs/839.out
> new file mode 100644
> index 00000000..f275cdcc
> --- /dev/null
> +++ b/tests/xfs/839.out
> @@ -0,0 +1,2 @@
> +QA output created by 839
> +syncfs: Input/output error
>
next prev parent reply other threads:[~2022-04-19 19:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-19 17:32 [PATCHSET v2 0/2] fstests: new tests for kernel 5.18 Darrick J. Wong
2022-04-19 17:32 ` [PATCH 1/2] xfs: make sure syncfs(2) passes back super_operations.sync_fs errors Darrick J. Wong
2022-04-19 18:17 ` Amir Goldstein
2022-04-19 19:10 ` Zorro Lang [this message]
2022-04-19 17:32 ` [PATCH 2/2] generic: ensure we drop suid after fallocate Darrick J. Wong
2022-04-19 18:40 ` Zorro Lang
-- strict thread matches above, loose matches on Subject: below --
2022-03-16 3:30 [PATCHSET 0/2] fstests: new tests for kernel 5.17 Darrick J. Wong
2022-03-16 3:30 ` [PATCH 1/2] xfs: make sure syncfs(2) passes back super_operations.sync_fs errors Darrick J. Wong
2022-03-23 2:44 ` Zorro Lang
2022-03-24 21:38 ` 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=20220419191014.ebcfzdbtg45fhg27@zlang-mailbox \
--to=zlang@redhat.com \
--cc=amir73il@gmail.com \
--cc=djwong@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=guan@eryu.me \
--cc=guaneryu@gmail.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