FS/XFS testing framework
 help / color / mirror / Atom feed
From: Anand Jain <anand.jain@oracle.com>
To: fdmanana@kernel.org, fstests@vger.kernel.org
Cc: linux-btrfs@vger.kernel.org, Filipe Manana <fdmanana@suse.com>
Subject: Re: [PATCH] btrfs/286: add missing calls to _scratch_dev_pool_put and _spare_dev_put
Date: Wed, 8 Mar 2023 16:05:36 +0800	[thread overview]
Message-ID: <675dc048-d823-2c24-51b3-8a10ae1744df@oracle.com> (raw)
In-Reply-To: <1933b829b03a6e489494706792e813b8db693577.1678189056.git.fdmanana@suse.com>

On 07/03/2023 19:38, fdmanana@kernel.org wrote:
> From: Filipe Manana <fdmanana@suse.com>
> 
> The test is doing a _scratch_dev_pool_get, which shrinks the list of
> devices in SCRATCH_DEV_POOL, but it's not calling _scratch_dev_pool_put
> before it finishes. This will result in subsequent tests (none at the
> moment however) getting a reduced list of devices in SCRATCH_DEV_POOL.
> 
> The same goes for the spare device, the test calls _spare_dev_get but
> it never calls _spare_dev_put.
> 
> So add the missing calls.
> 
> Signed-off-by: Filipe Manana <fdmanana@suse.com>
> ---
>   tests/btrfs/286 | 3 +++
>   1 file changed, 3 insertions(+)
> 
> diff --git a/tests/btrfs/286 b/tests/btrfs/286
> index fb805256..f1ee129c 100755
> --- a/tests/btrfs/286
> +++ b/tests/btrfs/286
> @@ -71,6 +71,9 @@ for t in "${_btrfs_profile_configs[@]}"; do
>   	workload "$t"
>   done
>   
> +_spare_dev_put
> +_scratch_dev_pool_put
> +
>   echo "Silence is golden"
>   
>   # success, all done

Looks good.

Reviewed-by: Anand Jain <anand.jain@oracle.com>

      reply	other threads:[~2023-03-08  8:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-07 11:38 [PATCH] btrfs/286: add missing calls to _scratch_dev_pool_put and _spare_dev_put fdmanana
2023-03-08  8:05 ` Anand Jain [this message]

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=675dc048-d823-2c24-51b3-8a10ae1744df@oracle.com \
    --to=anand.jain@oracle.com \
    --cc=fdmanana@kernel.org \
    --cc=fdmanana@suse.com \
    --cc=fstests@vger.kernel.org \
    --cc=linux-btrfs@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