public inbox for fstests@vger.kernel.org
 help / color / mirror / Atom feed
From: Eryu Guan <guaneryu@gmail.com>
To: fstests@vger.kernel.org
Subject: [ANNOUNCE] fstests: master branch updated to 52f9ebbda94d
Date: Sun, 07 May 2017 15:23:47 +0800	[thread overview]
Message-ID: <590ecb89.c225620a.b2144.8203@mx.google.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 2440 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. There're mainly new tests added in this update. The
overlay consistent inode tests has been improved extensively, new encryption
and xfs tests has been added. And _check_dmesg now could catch new "suspicious
RCU usage" message in dmesg, cephfs gained better attr test support. Many
thanks to all who have contributed and/or helped reviewed patches!

New failures I've noticed in this update:
- xfs/294 hangs (soft lockup) v4.11 kernel, which should be fixed in 4.12-rc1

Thanks,
Eryu

The new head of the master branch is commit:

52f9ebbda94d generic: test revalidation of encrypted dentries

New commits:

Amir Goldstein (6):
      [c2c9d7ef1adb] overlay/017: silence test output
      [3813cafb81db] overlay/017: fix some comments
      [8a76c404454f] overlay/017: use af_unix to create socket test file
      [dca98801ed2e] overlay/017: create helpers to record and check inode numbers
      [08253234856c] overlay/017: verify constant inode number after rename
      [cf0e25209dcc] overlay/017: test persistent inode numbers after mount cycle

Eric Biggers (2):
      [3c309f26fbd7] common/rc: catch updated suspicious RCU usage message in _check_dmesg()
      [52f9ebbda94d] generic: test revalidation of encrypted dentries

Eric Sandeen (2):
      [9343320e6788] xfs: test fragmented multi-fsb readdir
      [54ac0dd3086d] punch-alternating: add some options

Luis Henriques (1):
      [5fcc706aab43] attr: add support for cephfs


Code Diffstat:

 .gitignore                     |   1 +
 common/attr                    |  24 +++++--
 common/encrypt                 |  42 ++++++++---
 common/rc                      |   4 +-
 src/Makefile                   |   2 +-
 src/punch-alternating.c        |  47 ++++++++++---
 src/t_encrypted_d_revalidate.c | 122 ++++++++++++++++++++++++++++++++
 tests/generic/429              | 154 +++++++++++++++++++++++++++++++++++++++++
 tests/generic/429.out          |  37 ++++++++++
 tests/generic/group            |   1 +
 tests/overlay/017              |  86 ++++++++++++++++++-----
 tests/overlay/017.out          |   7 +-
 tests/xfs/294                  | 118 +++++++++++++++++++++++++++++++
 tests/xfs/294.out              |   2 +
 tests/xfs/group                |   1 +
 15 files changed, 598 insertions(+), 50 deletions(-)
--
Eryu Guan
eguan@redhat.com

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 801 bytes --]

                 reply	other threads:[~2017-05-07 23:58 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=590ecb89.c225620a.b2144.8203@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