From: Marcos Paulo de Souza <marcos@mpdesouza.com>
To: dsterba@suse.com, nborisov@suse.com, linux-btrfs@vger.kernel.org,
fstests@vger.kernel.org, guaneryu@gmail.com
Cc: Marcos Paulo de Souza <mpdesouza@suse.com>
Subject: [ fstests PATCHv3 0/2] btrfs: Test subvolume delete by id feature
Date: Mon, 24 Feb 2020 00:13:39 -0300 [thread overview]
Message-ID: <20200224031341.27740-1-marcos@mpdesouza.com> (raw)
From: Marcos Paulo de Souza <mpdesouza@suse.com>
Changes from v2:
* Added Reviewed-by from Nikolay to patch 0001
* Changed awk to $AWK_PROG, suggested by Eryu
* Changed _run_btrfs_util_prog to $BTRFS_UTIL_PROG, suggested by Eryu
* Use _scratch_unmount instead of executing umount by hand, sugested by Eryu
* Created a local function to delete and list subvolumes, suggested by Eryu
Changes from v1:
* Added some prints printing what is being tested
* The test now uses the _btrfs_get_subvolid to get subvolumeids instead of using
plain integers
* New patch expanding the funtionality of _require_btrfs_command, which now
check for argument of subcommands
Marcos Paulo de Souza (2):
common: btrfs: Improve _require_btrfs_command
btrfs: Test subvolume delete --subvolid feature
common/btrfs | 13 ++++++--
tests/btrfs/203 | 73 +++++++++++++++++++++++++++++++++++++++++++++
tests/btrfs/203.out | 14 +++++++++
tests/btrfs/group | 1 +
4 files changed, 99 insertions(+), 2 deletions(-)
create mode 100755 tests/btrfs/203
create mode 100644 tests/btrfs/203.out
--
2.25.0
next reply other threads:[~2020-02-24 3:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-24 3:13 Marcos Paulo de Souza [this message]
2020-02-24 3:13 ` [ fstests PATCHv3 1/2] common: btrfs: Improve _require_btrfs_command Marcos Paulo de Souza
2020-02-24 19:54 ` Johannes Thumshirn
2020-03-01 13:36 ` Eryu Guan
2020-02-24 3:13 ` [ fstests PATCHv3 2/2] btrfs: Test subvolume delete --subvolid feature Marcos Paulo de Souza
2020-03-01 13:54 ` Eryu Guan
2020-03-01 17:06 ` Marcos Paulo de Souza
2020-03-08 15:12 ` Eryu Guan
2020-03-08 15:15 ` Eryu Guan
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=20200224031341.27740-1-marcos@mpdesouza.com \
--to=marcos@mpdesouza.com \
--cc=dsterba@suse.com \
--cc=fstests@vger.kernel.org \
--cc=guaneryu@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=mpdesouza@suse.com \
--cc=nborisov@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;
as well as URLs for NNTP newsgroup(s).