From: Dave Chinner <david@fromorbit.com>
To: xfs@oss.sgi.com
Cc: linux-ext4@vger.kernel.org, linux-btrfs@vger.kernel.org
Subject: [ANNOUNCE] xfstests: master branch updated to 10fd79a
Date: Tue, 13 May 2014 16:30:18 +1000 [thread overview]
Message-ID: <20140513063018.GB5421@dastard> (raw)
Hi folks,
The xfstests repository at git://oss.sgi.com/xfs/cmds/xfstests has
just been updated. Patches often get missed, so please check if your
outstanding patches were in this update. If they have not been in
this update, please resubmit them to xfs@oss.sgi.com so they can be
picked up in the next update.
The new head of the master branch is commit:
10fd79a locktest: add a F_GETLK vs. openmode test
New Commits:
Brian Foster (5):
[2a52b8f] xfs/030: filter out extra repair noise for finobt enabled fs'
[9d5cb63] common: add _require_xfs_[mkfs_]finobt() checks for finobt tests
[01fbf44] repair: filter agno/ino repair output for finobt
[d95ecb0] xfs/010: test repair for finobt corruption
[c141570] xfs/013: stress the free inode btree
Eryu Guan (1):
[ec08236] common: new function to get real device path name and basename
Jeff Layton (4):
[2baab36] locktest: don't assume that F_OPEN should use O_RDWR
[ece564a] locktest: set f_fd to INVALID_HANDLE on close
[fe7056d] locktest: consolidate do_lock and do_unlock, and add ability to F_GETLK
[10fd79a] locktest: add a F_GETLK vs. openmode test
Josef Bacik (2):
[0fd4705] common: fix flink check
[b6689ad] config: fix selinux context handling
Namjae Jeon (1):
[995a459] fsstress: fix incorrect if condition check for collapse range mode
Theodore Ts'o (1):
[9f35155] check: add support for an external file containing tests to exclude
Wang Shilong (1):
[49398f8] btrfs: add regression test for inode cache vs tree log
hch@infradead.org (1):
[7f82a5f] common: use a relative path to fsstress
Code Diffstat:
check | 6 ++
common/config | 18 +++---
common/rc | 36 ++++++++++++
common/repair | 2 +
ltp/fsstress.c | 2 +-
src/locktest.c | 125 +++++++++++++++++++-----------------------
tests/btrfs/049 | 109 ++++++++++++++++++++++++++++++++++++
tests/btrfs/049.out | 1 +
tests/btrfs/group | 1 +
tests/ext4/305 | 2 +-
tests/generic/009 | 2 +-
tests/generic/019 | 4 +-
tests/generic/285 | 2 +-
tests/generic/312 | 2 +-
tests/xfs/010 | 133 ++++++++++++++++++++++++++++++++++++++++++++
tests/xfs/010.out | 57 +++++++++++++++++++
tests/xfs/013 | 155 ++++++++++++++++++++++++++++++++++++++++++++++++++++
tests/xfs/013.out | 7 +++
tests/xfs/030 | 3 +-
tests/xfs/group | 2 +
20 files changed, 582 insertions(+), 87 deletions(-)
create mode 100644 tests/btrfs/049
create mode 100644 tests/btrfs/049.out
create mode 100755 tests/xfs/010
create mode 100644 tests/xfs/010.out
create mode 100755 tests/xfs/013
create mode 100644 tests/xfs/013.out
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
reply other threads:[~2014-05-13 6:30 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20140513063018.GB5421@dastard \
--to=david@fromorbit.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-ext4@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox