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 95c924c65113
Date: Sun, 07 Jan 2018 23:58:58 +0800	[thread overview]
Message-ID: <5a5243c9.8467620a.10c7f.cc40@mx.google.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 3151 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. clonerange and deduperange operations are added to
fsstress in this update, so we get more test coverage on FICLONERANGE and
FIDEDUPERANGE syscalls. Two new tests that run fsstress are added too, one runs
fsstress on dmerror device to simulate disk falures and another runs fsstress
in write-only mode. We also have two new ext4 regression tests on DAX mount,
and a new btrfs test on raid6 scrub code.

New failures I've noticed in this update:
- generic/475 sometimes fails on ext4, I saw ext4 corruption after test (around
  20% reproducibility)
- generic/232 fails post-test fsck on reflink enabled XFS, I guess it has
  something to do with the new clonerange and deduperange operations
- generic/083, generic/269 and generic/270 would hang (soft lockup) on reflink
  enabled XFS, they all exercise behavior near ENOSPC, and generic/269 would
  hit the soft lockup more easily
- btrfs/158 fails on btrfs, the fixes are referenced in the test

Perhaps there're other failures that're caused by the new clone and dedupe
operations in fsstress, please report and/or contribute patches if you think
that's a case bug that needs fix.

Thanks,
Eryu

The new head of the master branch is commit:

95c924c65113 ext4: test for inline data + DAX corruption

New commits:

Darrick J. Wong (4):
      [ce02f1b2f8ed] generic: test error shutdown while stressing filesystem
      [e76e13ce8c0b] fsstress: implement the clonerange/deduperange ioctls
      [3b1382f992bf] generic: run a long-soak write-only fsstress test
      [451504891031] xfs/068: fix clonerange problems in file/dir count output

Liu Bo (1):
      [70138c383bf5] btrfs: make sure scrub fixes raid6 corruption

Luis Henriques (1):
      [ebe1aa88a197] generic/050: fix _require_local_device $SCRATCH_DEV check order

Ross Zwisler (2):
      [750a24e99e48] ext4: test for DAX + journaling corruption
      [95c924c65113] ext4: test for inline data + DAX corruption


Code Diffstat:

 .gitignore                          |   2 +
 common/dump                         |  11 +
 ltp/fsstress.c                      | 391 ++++++++++++++++++++++++++++++++++++
 src/Makefile                        |   3 +-
 src/t_ext4_dax_inline_corruption.c  |  70 +++++++
 src/t_ext4_dax_journal_corruption.c | 102 ++++++++++
 tests/btrfs/158                     | 114 +++++++++++
 tests/btrfs/158.out                 |  10 +
 tests/btrfs/group                   |   1 +
 tests/ext4/030                      |  74 +++++++
 tests/ext4/030.out                  |   2 +
 tests/ext4/031                      |  86 ++++++++
 tests/ext4/031.out                  |   2 +
 tests/ext4/group                    |   2 +
 tests/generic/050                   |   2 +-
 tests/generic/475                   |  97 +++++++++
 tests/generic/475.out               |   2 +
 tests/generic/476                   |  64 ++++++
 tests/generic/476.out               |   2 +
 tests/generic/group                 |   2 +
 20 files changed, 1037 insertions(+), 2 deletions(-)
--
Eryu Guan
eguan@redhat.com

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

                 reply	other threads:[~2018-01-07 15:59 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=5a5243c9.8467620a.10c7f.cc40@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