From: Jeff Mahoney <jeffm@suse.com>
To: xfs@oss.sgi.com
Cc: Josef Bacik <jbacik@fusionio.com>, linux-btrfs@vger.kernel.org
Subject: [patch 0/3] xfstests: for btrfs publishing/export patchset (v4)
Date: Tue, 29 Oct 2013 15:26:53 -0400 [thread overview]
Message-ID: <20131029192653.194827430@suse.com> (raw)
These are the tests that Josef requested accompany the submission of
the btrfs publishing/export patchset[1].
021: Test new global metadata reservation ioctl
022: Test new sysfs exporting of allocation and device membership
023: Test new sysfs exporting of feature bits
024: Test setting/clearing feature bits via ioctl
025: Test setting/clearing feature bits via sysfs
As part of the ioctl testing, I added a helper that can be extended
easily to export simple information via ioctl. This means that the
tests can be independent of btrfsprogs version or its output formatting.
V2:
- Used next numbers in sequence
- Better commit messages
- Fixed handling of the missing feature cases
- Fixed issues raised in Josef's review
V3:
- Fixed missing output in btrfs/023 when the ioctls arent't supported
- Fixed missing umount introduced in V2
V4:
- I was running the tests directly, not through check and didn't catch these:
- Fixed incorrect output from 022 while running under check
- Added tests to group file
-Jeff
[1] http://thread.gmane.org/gmane.comp.file-systems.btrfs/29307
WARNING: multiple messages have this Message-ID (diff)
From: Jeff Mahoney <jeffm@suse.com>
To: xfs@oss.sgi.com
Cc: linux-btrfs@vger.kernel.org, Josef Bacik <jbacik@fusionio.com>
Subject: [patch 0/3] xfstests: for btrfs publishing/export patchset (v4)
Date: Tue, 29 Oct 2013 15:26:53 -0400 [thread overview]
Message-ID: <20131029192653.194827430@suse.com> (raw)
These are the tests that Josef requested accompany the submission of
the btrfs publishing/export patchset[1].
021: Test new global metadata reservation ioctl
022: Test new sysfs exporting of allocation and device membership
023: Test new sysfs exporting of feature bits
024: Test setting/clearing feature bits via ioctl
025: Test setting/clearing feature bits via sysfs
As part of the ioctl testing, I added a helper that can be extended
easily to export simple information via ioctl. This means that the
tests can be independent of btrfsprogs version or its output formatting.
V2:
- Used next numbers in sequence
- Better commit messages
- Fixed handling of the missing feature cases
- Fixed issues raised in Josef's review
V3:
- Fixed missing output in btrfs/023 when the ioctls arent't supported
- Fixed missing umount introduced in V2
V4:
- I was running the tests directly, not through check and didn't catch these:
- Fixed incorrect output from 022 while running under check
- Added tests to group file
-Jeff
[1] http://thread.gmane.org/gmane.comp.file-systems.btrfs/29307
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2013-10-29 19:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-29 19:26 Jeff Mahoney [this message]
2013-10-29 19:26 ` [patch 0/3] xfstests: for btrfs publishing/export patchset (v4) Jeff Mahoney
2013-10-29 19:26 ` [patch 1/3] xfstests: btrfs/021: test global metadata reservation reporting Jeff Mahoney
2013-10-29 19:26 ` Jeff Mahoney
2013-10-29 19:26 ` [patch 2/3] xfstests: btrfs/022: test sysfs exports of allocation and device membership info Jeff Mahoney
2013-10-29 19:26 ` Jeff Mahoney
2013-10-29 19:26 ` [patch 3/3] xfstests: btrfs/023,024,025: test feature ioctl and sysfs interfaces Jeff Mahoney
2013-10-29 19:26 ` [patch 3/3] xfstests: btrfs/023, 024, 025: " Jeff Mahoney
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=20131029192653.194827430@suse.com \
--to=jeffm@suse.com \
--cc=jbacik@fusionio.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=xfs@oss.sgi.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.