From: Eryu Guan <guaneryu@gmail.com>
To: fstests@vger.kernel.org
Subject: [ANNOUNCE] fstests: master branch updated to 6458922bb5dc
Date: Mon, 06 Jan 2020 18:24:46 +0800 [thread overview]
Message-ID: <5e130af3.1c69fb81.85cfc.0d28@mx.google.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2834 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. This update mainly pulls in the fscrypt improvements
and new tests from Eric Biggers. There're also some new tests for btrfs & xfs,
and some random bug fixes.
The new btrfs test (btrfs/202) currently fails with v5.5-rc5 kernel, the fix is
not upstreamed yet.
There're still some review backlogs in my to-review list, my apology for the
delay!
Thanks,
Eryu
The new head of the master branch is commit:
6458922bb5dc btrfs: regression test for subvol deletion after rename
New commits:
Darrick J. Wong (2):
[29e2be05501f] common/dmerror: always try to resume device
[c4802d4a53a9] fsx: fix range overlap check
Eric Biggers (5):
[80bc5f9d790b] fscrypt-crypt-util: create key_and_iv_params structure
[faf3abfe3f16] fscrypt-crypt-util: add HKDF context constants
[799d6b506df7] common/encrypt: create named variables for UAPI constants
[a5d24c8bdf94] common/encrypt: support verifying ciphertext of IV_INO_LBLK_64 policies
[0335928b8c93] generic: verify ciphertext of IV_INO_LBLK_64 encryption policies
Eric Sandeen (1):
[7b3ddeec674e] fstests: verify that xfs_growfs can operate on mounted device node
J. Bruce Fields (1):
[dda94e8088a7] generic/529: use an ACL that doesn't confuse NFS
Johannes Thumshirn (1):
[6a31c46b1a44] btrfs/139: require 2GB scratch dev
Josef Bacik (1):
[6458922bb5dc] btrfs: regression test for subvol deletion after rename
Qu Wenruo (1):
[996e2632443d] btrfs/14[01]: Use proper helper to get both devid and physical for corruption
Yang Xu (2):
[c09db96d31f2] generic/386: fill missing brackets in awk
[64954c0ead68] generic/590: skip test if kernel doesn't support realtime
Code Diffstat:
common/dmerror | 21 +++++--
common/encrypt | 126 ++++++++++++++++++++++++++++++---------
ltp/fsx.c | 14 ++++-
src/fscrypt-crypt-util.c | 151 ++++++++++++++++++++++++++++++++++-------------
src/t_attr_corruption.c | 2 +-
tests/btrfs/139 | 3 +-
tests/btrfs/140 | 34 ++++++++---
tests/btrfs/140.out | 2 -
tests/btrfs/141 | 35 ++++++++---
tests/btrfs/141.out | 2 -
tests/btrfs/202 | 57 ++++++++++++++++++
tests/btrfs/202.out | 4 ++
tests/btrfs/group | 1 +
tests/generic/386 | 2 +-
tests/generic/590 | 8 ++-
tests/generic/592 | 43 ++++++++++++++
tests/generic/592.out | 6 ++
tests/generic/group | 1 +
tests/xfs/149 | 101 +++++++++++++++++++++++++++++++
tests/xfs/149.out | 16 +++++
tests/xfs/group | 1 +
21 files changed, 531 insertions(+), 99 deletions(-)
--
Eryu Guan
guaneryu@gmail.com
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
reply other threads:[~2020-01-06 10:24 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=5e130af3.1c69fb81.85cfc.0d28@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 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.