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 249cc51
Date: Mon, 14 Apr 2014 10:49:38 +1000 [thread overview]
Message-ID: <20140414004938.GE27694@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.
This update includes tests for the new renameat2 syscall, and a
bunch of fixes for the new config file format infrastructure.
The new head of the master branch is commit:
249cc51 generic: add renameat2 system call number for i386
New Commits:
Alexander Tsvetkov (1):
[7e07c4b] generic/204: correct log size for XFS
Eric Whitney (2):
[2e9061f] generic/300: add fallocate() checks
[f729616] generic/311: add fallocate() check
Eryu Guan (1):
[9f1a8e7] ext4/306: disable 64bit feature too
Lukas Czerner (6):
[f00a444] config: Fix SCRATCH_DEV_POOL handling
[7407717] config: Unset SCRATCH_DEV when deduced from SCRATCH_DEV_POOL
[e0f5daf] config: Fix setting FSTYP automatically
[5138e74] config: fix specifying configuration value with equality sign
[ed6d096] generic/022: Fix output file
[a0e2d8e] config: Add -s option to run only specified sections
Miklos Szeredi (4):
[413f501] common: add infrastructure for renameat2 syscall tests
[bdf2150] generic: check plain renameat2 syscall
[1f98dd0] generic: check noreplace renameat2 syscall
[3c9cd13] generic: check cross renameat2 syscall
Theodore Ts'o (2):
[dd8556c] generic/004: fix filtering of expected error message
[249cc51] generic: add renameat2 system call number for i386
Wanlong Gao (1):
[610e44c] check: fix wallclock wrapping problem
Code Diffstat:
.gitignore | 1 +
README.config-sections | 30 ++++++++++++
check | 26 ++++++----
common/config | 35 +++++++++++---
common/renameat2 | 129 +++++++++++++++++++++++++++++++++++++++++++++++++
configure.ac | 2 +
src/Makefile | 3 +-
src/renameat2.c | 106 ++++++++++++++++++++++++++++++++++++++++
tests/ext4/306 | 2 +-
tests/generic/004 | 2 +-
tests/generic/004.out | 2 +-
tests/generic/022.out | 2 +-
tests/generic/023 | 57 ++++++++++++++++++++++
tests/generic/023.out | 51 +++++++++++++++++++
tests/generic/024 | 64 ++++++++++++++++++++++++
tests/generic/024.out | 51 +++++++++++++++++++
tests/generic/025 | 64 ++++++++++++++++++++++++
tests/generic/025.out | 51 +++++++++++++++++++
tests/generic/204 | 4 +-
tests/generic/300 | 7 +++
tests/generic/311 | 6 ++-
tests/generic/group | 3 ++
22 files changed, 672 insertions(+), 26 deletions(-)
create mode 100644 common/renameat2
create mode 100644 src/renameat2.c
create mode 100755 tests/generic/023
create mode 100644 tests/generic/023.out
create mode 100755 tests/generic/024
create mode 100644 tests/generic/024.out
create mode 100755 tests/generic/025
create mode 100644 tests/generic/025.out
mode change 100644 => 100755 tests/generic/311
--
Dave Chinner
david@fromorbit.com
next reply other threads:[~2014-04-14 0:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-14 0:49 Dave Chinner [this message]
2014-04-14 1:22 ` [ANNOUNCE] xfstests: master branch updated to 8874560 Dave Chinner
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=20140414004938.GE27694@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;
as well as URLs for NNTP newsgroup(s).