All of lore.kernel.org
 help / color / mirror / Atom feed
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: tests for btrfs publishing/export patchset
Date: Fri, 25 Oct 2013 16:52:46 -0400	[thread overview]
Message-ID: <20131025205246.269327744@suse.com> (raw)

These are the tests that Josef requested accompany the submission of
the btrfs publishing/export patchset[1].

100: Test new global metadata reservation ioctl
101: Test new sysfs exporting of allocation and device membership
102: Test new sysfs exporting of feature bits
103: Test setting/clearing feature bits via ioctl
104: 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.

-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: tests for btrfs publishing/export patchset
Date: Fri, 25 Oct 2013 16:52:46 -0400	[thread overview]
Message-ID: <20131025205246.269327744@suse.com> (raw)

These are the tests that Josef requested accompany the submission of
the btrfs publishing/export patchset[1].

100: Test new global metadata reservation ioctl
101: Test new sysfs exporting of allocation and device membership
102: Test new sysfs exporting of feature bits
103: Test setting/clearing feature bits via ioctl
104: 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.

-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

             reply	other threads:[~2013-10-25 20:56 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-25 20:52 Jeff Mahoney [this message]
2013-10-25 20:52 ` [patch 0/3] xfstests: tests for btrfs publishing/export patchset Jeff Mahoney
2013-10-25 20:52 ` [patch 1/3] [PATCH 1/3] xfstests: add test for global metadata reservation publishing Jeff Mahoney
2013-10-25 20:52   ` Jeff Mahoney
2013-10-28 15:59   ` Josef Bacik
2013-10-28 15:59     ` Josef Bacik
2013-10-28 19:55     ` Jeff Mahoney
2013-10-28 19:55       ` Jeff Mahoney
2013-10-25 20:52 ` [patch 2/3] [PATCH 2/3] xfstests: add test for sysfs publication of btrfs info Jeff Mahoney
2013-10-25 20:52   ` Jeff Mahoney
2013-10-28 15:53   ` Josef Bacik
2013-10-28 15:53     ` Josef Bacik
2013-10-25 20:52 ` [patch 3/3] [PATCH 3/3] xfstests: add tests for new feature ioctl and sysfs interfaces Jeff Mahoney
2013-10-25 20:52   ` Jeff Mahoney
2013-10-28 16:02   ` Josef Bacik
2013-10-28 16:02     ` Josef Bacik
2013-10-25 21:21 ` [patch 0/3] xfstests: tests for btrfs publishing/export patchset Jeff Mahoney
2013-10-25 21:21   ` 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=20131025205246.269327744@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.