public inbox for fstests@vger.kernel.org
 help / color / mirror / Atom feed
From: David Disseldorp <ddiss@suse.de>
To: Qu Wenruo <wqu@suse.com>
Cc: linux-btrfs@vger.kernel.org, fstests@vger.kernel.org
Subject: Re: [PATCH] fstests: btrfs/220: fix the test failure due to new default mount option
Date: Fri, 9 Dec 2022 09:37:28 +0100	[thread overview]
Message-ID: <20221209093728.230a7d4b@echidna.fritz.box> (raw)
In-Reply-To: <20221209060510.29557-1-wqu@suse.com>

Hi Qu,

On Fri,  9 Dec 2022 14:05:10 +0800, Qu Wenruo wrote:

> [BUG]
> The latest misc-next tree will make test case btrfs/220 fail with the
> following error messages:
> 
> btrfs/220 15s ... - output mismatch (see ~/xfstests/results//btrfs/220.out.bad)
>     --- tests/btrfs/220.out	2022-05-11 09:55:30.749999997 +0800
>     +++ ~/xfstests/results//btrfs/220.out.bad	2022-12-09 13:57:23.706666671 +0800
>     @@ -1,2 +1,5 @@
>      QA output created by 220
>     +Unexepcted mount options, checking for 'rw,relatime,discard=async,space_cache=v2,subvolid=5,subvol=/' in 'rw,relatime,space_cache=v2,subvolid=5,subvol=/' using 'nodiscard'
>     +Unexepcted mount options, checking for 'rw,relatime,discard=async,space_cache=v2,subvolid=5,subvol=/' in 'rw,relatime,space_cache=v2,subvolid=5,subvol=/' using 'nodiscard'
>     +Unexepcted mount options, checking for 'rw,relatime,discard=async,space_cache=v2,subvolid=5,subvol=/' in 'rw,relatime,space_cache=v2,subvolid=5,subvol=/' using 'nodiscard'
>      Silence is golden
>     ...
>     (Run 'diff -u ~/xfstests/tests/btrfs/220.out ~/xfstests/results//btrfs/220.out.bad'  to see the entire diff)
> Ran: btrfs/220
> Failures: btrfs/220
> Failed 1 of 1 tests
> 
> [CAUSE]
> Since patch "btrfs: auto enable discard=async when possible", which is
> already in the maintainer's tree for next merge window, btrfs will
> automatically enable asynchronous discard for devices which supports
> discard.
> 
> This makes our $DEFAULT_OPTS to have "discard=async" in it.
> 
> While for "nodiscard" mount option, we will completely disable all
> discard, causing the above mismatch.
> 
> [FIX]
> Fix it by introducing $DEFAULT_NODISCARD_OPTS specifically for
> "nodiscard" mount option.
> 
> If async discard is not enabled by default, $DEFAULT_NODISCARD_OPTS will
> be the same as $DEFAULT_OPTS, thus everything would work as usual.
> 
> If async discard is enabled by default, $DEFAULT_NODISCARD_OPTS will
> have that removed, so for "nodiscard" we can use $DEFAULT_NODISCARD_OPTS
> as expected mount options.
> 
> Signed-off-by: Qu Wenruo <wqu@suse.com>
> ---
>  tests/btrfs/220 | 10 ++++++++--
>  1 file changed, 8 insertions(+), 2 deletions(-)
> 
> diff --git a/tests/btrfs/220 b/tests/btrfs/220
> index 4d94ccd6..30ca06f6 100755
> --- a/tests/btrfs/220
> +++ b/tests/btrfs/220
> @@ -280,10 +280,10 @@ test_revertible_options()
>  	if [ "$enable_discard_sync" = true ]; then
>  		test_roundtrip_mount "discard" "discard" "discard=sync" "discard"
>  		test_roundtrip_mount "discard=async" "discard=async" "discard=sync" "discard"
> -		test_roundtrip_mount "discard=sync" "discard" "nodiscard" "$DEFAULT_OPTS"
> +		test_roundtrip_mount "discard=sync" "discard" "nodiscard" "$DEFAULT_NODISCARD_OPTS"
>  	else
>  		test_roundtrip_mount "discard" "discard" "discard" "discard"
> -		test_roundtrip_mount "discard" "discard" "nodiscard" "$DEFAULT_OPTS"
> +		test_roundtrip_mount "discard" "discard" "nodiscard" "$DEFAULT_NODISCARD_OPTS"
>  	fi
>  
>  	test_roundtrip_mount "enospc_debug" "enospc_debug" "noenospc_debug" "$DEFAULT_OPTS"
> @@ -344,6 +344,12 @@ _scratch_mount
>  DEFAULT_OPTS=$(cat /proc/self/mounts | grep $SCRATCH_MNT | \
>  		$AWK_PROG '{ print $4 }')
>  
> +# Since 63a7cb130718 ("btrfs: auto enable discard=async when possible"),
> +# "discard=async" will be automatically enabled if the device supports.
> +# This can screw up our test against nodiscard options, thus remove the
> +# default "discard=async" mount option for "nodiscard" tests.
> +DEFAULT_NODISCARD_OPTS=$(echo -n "$DEFAULT_OPTS" | $SED_PROG 's/,discard=async//')

Comma placement here looks a little fragile, but I suppose discard won't
normally be listed first.
FWIW, substring removal is also possible in plain bash e.g.:
  DEFAULT_NODISCARD_OPTS="${DEFAULT_OPTS/,discard=async/}"
Either way...

Reviewed-by: David Disseldorp <ddiss@suse.de>

> +
>  $BTRFS_UTIL_PROG subvolume create "$SCRATCH_MNT/vol1" > /dev/null
>  touch "$SCRATCH_MNT/vol1/file.txt"
>  _scratch_unmount


  reply	other threads:[~2022-12-09  8:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-09  6:05 [PATCH] fstests: btrfs/220: fix the test failure due to new default mount option Qu Wenruo
2022-12-09  8:37 ` David Disseldorp [this message]
2022-12-23  0:06 ` Qu Wenruo

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=20221209093728.230a7d4b@echidna.fritz.box \
    --to=ddiss@suse.de \
    --cc=fstests@vger.kernel.org \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=wqu@suse.com \
    /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