From: Filipe Manana <fdmanana@kernel.org>
To: Sidong Yang <realwakka@gmail.com>
Cc: linux-btrfs@vger.kernel.org, fstests@vger.kernel.org,
Shinichiro Kawasaki <shinichiro.kawasaki@wdc.com>,
"dsterba@suse.cz" <dsterba@suse.cz>
Subject: Re: [PATCH v2] btrfs: add test for enable/disable quota and create/destroy qgroup repeatedly
Date: Wed, 2 Mar 2022 15:22:31 +0000 [thread overview]
Message-ID: <Yh+Lt4HfHBO18Ifh@debian9.Home> (raw)
In-Reply-To: <20220302140548.1150-1-realwakka@gmail.com>
On Wed, Mar 02, 2022 at 02:05:48PM +0000, Sidong Yang wrote:
> Test enable/disable quota and create/destroy qgroup repeatedly in
> parallel and confirm it does not cause kernel hang. It only happens
> in kernel staring with kernel 5.17-rc3. This is a regression test
> for the problem reported to linux-btrfs list [1].
>
> The hang was recreated using the test case and fixed by kernel patch
> titled
>
> btrfs: qgroup: fix deadlock between rescan worker and remove qgroup
>
> [1] https://lore.kernel.org/linux-btrfs/20220228014340.21309-1-realwakka@gmail.com/
>
> Signed-off-by: Sidong Yang <realwakka@gmail.com>
> ---
> v2 : fix changelog, comments, no wait pids argument
> ---
> tests/btrfs/262 | 40 ++++++++++++++++++++++++++++++++++++++++
> tests/btrfs/262.out | 2 ++
> 2 files changed, 42 insertions(+)
> create mode 100755 tests/btrfs/262
> create mode 100644 tests/btrfs/262.out
>
> diff --git a/tests/btrfs/262 b/tests/btrfs/262
> new file mode 100755
> index 00000000..8953a28e
> --- /dev/null
> +++ b/tests/btrfs/262
> @@ -0,0 +1,40 @@
> +#! /bin/bash
> +# SPDX-License-Identifier: GPL-2.0
> +# Copyright (c) 2022 Sidong Yang. All Rights Reserved.
> +#
> +# FS QA Test 262
> +#
> +# Test that running qgroup enable, create, destroy, and disable commands in
> +# parallel doesn't result in a deadlock, a crash or any filesystem
> +# inconsistency.
> +#
> +. ./common/preamble
> +_begin_fstest auto quick qgroup
> +
> +# Import common functions.
> +. ./common/filter
> +
> +# real QA test starts here
> +
> +_supported_fs btrfs
> +
> +_require_scratch
> +
> +_scratch_mkfs > /dev/null 2>&1
> +_scratch_mount
> +
> +for ((i = 0; i < 200; i++)); do
> + $BTRFS_UTIL_PROG quota enable $SCRATCH_MNT 2>> $seqres.full &
> + $BTRFS_UTIL_PROG qgroup create 1/0 $SCRATCH_MNT 2>> $seqres.full &
> + $BTRFS_UTIL_PROG qgroup destroy 1/0 $SCRATCH_MNT 2>> $seqres.full &
> + $BTRFS_UTIL_PROG quota disable $SCRATCH_MNT 2>> $seqres.full &
> +done
> +
> +wait
> +
> +_scratch_unmount
The fstests framework will also do the unmount, so this can be removed.
You don't need to send a new patch version just to remove that, Eryu
can probably amend the patch when he picks it up.
Anyway, it looks good and it works as expected.
Reviewed-by: Filipe Manana <fdmanana@suse.com>
Thanks for making the test case.
> +
> +# success, all done
> +echo "Silence is golden"
> +status=0
> +exit
> diff --git a/tests/btrfs/262.out b/tests/btrfs/262.out
> new file mode 100644
> index 00000000..404badc3
> --- /dev/null
> +++ b/tests/btrfs/262.out
> @@ -0,0 +1,2 @@
> +QA output created by 262
> +Silence is golden
> --
> 2.25.1
>
next prev parent reply other threads:[~2022-03-02 15:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-02 14:05 [PATCH v2] btrfs: add test for enable/disable quota and create/destroy qgroup repeatedly Sidong Yang
2022-03-02 15:22 ` Filipe Manana [this message]
2022-03-03 0:51 ` Shinichiro Kawasaki
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=Yh+Lt4HfHBO18Ifh@debian9.Home \
--to=fdmanana@kernel.org \
--cc=dsterba@suse.cz \
--cc=fstests@vger.kernel.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=realwakka@gmail.com \
--cc=shinichiro.kawasaki@wdc.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