From: Eryu Guan <guaneryu@gmail.com>
To: fstests@vger.kernel.org
Subject: [ANNOUNCE] fstests: master branch updated to b09ba3318ebb
Date: Mon, 02 Nov 2020 00:31:37 +0800 [thread overview]
Message-ID: <5f9ee2fa.1c69fb81.abde7.f5f4@mx.google.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2347 bytes --]
Hi all,
The master branch of the xfstests repository at:
git://git.kernel.org/pub/scm/fs/xfs/xfstests-dev.git
have just been updated. We're having more ceph-specific copy_file_range tests
in this update, one fs-encryption test and one new ext4 test. Others are random
bug fixes.
Thanks,
Eryu
The new head of the master branch is commit:
b09ba3318ebb generic: test that encryption nonces are unique and random
New commits:
Eric Biggers (4):
[c8e29174c923] generic/397: remove workarounds for wrong error codes
[faf1f9356ef1] generic/395: remove workarounds for wrong error codes
[59b43407a9cc] generic/398: remove workarounds for wrong error codes
[b09ba3318ebb] generic: test that encryption nonces are unique and random
Filipe Manana (1):
[eb7f35472b2e] fstests: add missing remove of the $seqres.full file for some tests
Luis Henriques (3):
[10f3f9707cca] ceph: add copy_file_range (remote copy operation) testing
[5f460552c8f4] ceph: test combination of copy_file_range with truncate
[fce32d21f868] ceph: test copy_file_range with infile = outfile
Xiao Yang (1):
[27774be17b64] ext4: Add a test for inline_data vs. DAX inode flag
Zorro Lang (1):
[f81829d98ca6] common/repair: filter unknown block state properly
Code Diffstat:
common/ceph | 23 +++++
common/rc | 1 +
common/repair | 4 +-
tests/btrfs/033 | 3 +
tests/btrfs/036 | 3 +
tests/btrfs/114 | 3 +
tests/btrfs/115 | 3 +
tests/btrfs/205 | 3 +
tests/ceph/001 | 233 ++++++++++++++++++++++++++++++++++++++++++++++++++
tests/ceph/001.out | 129 ++++++++++++++++++++++++++++
tests/ceph/002 | 79 +++++++++++++++++
tests/ceph/002.out | 8 ++
tests/ceph/003 | 116 +++++++++++++++++++++++++
tests/ceph/003.out | 11 +++
tests/ceph/group | 3 +
tests/ext4/047 | 56 ++++++++++++
tests/ext4/047.out | 2 +
tests/ext4/group | 1 +
tests/generic/395 | 31 ++-----
tests/generic/397 | 25 ++----
tests/generic/398 | 35 ++------
tests/generic/613 | 118 +++++++++++++++++++++++++
tests/generic/613.out | 16 ++++
tests/generic/group | 1 +
tests/shared/298 | 3 +
25 files changed, 840 insertions(+), 70 deletions(-)
--
Eryu Guan
guaneryu@gmail.com
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
reply other threads:[~2020-11-01 16:31 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=5f9ee2fa.1c69fb81.abde7.f5f4@mx.google.com \
--to=guaneryu@gmail.com \
--cc=fstests@vger.kernel.org \
/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