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 ee55ddd38f01
Date: Sun, 14 Jan 2018 23:41:49 +0800	[thread overview]
Message-ID: <5a5b7a46.097e630a.f6df2.94c0@mx.google.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 2593 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. One notable change is that we're getting 9pfs support
in fstests, thanks to Toumas Tynkkynen! Other updates are normal new tests and
bug fixes/improvements patches.

I didn't notice any new failures introduced by this update.

Thanks,
Eryu

The new head of the master branch is commit:

ee55ddd38f01 fstests: Add 9p network filesystem support

New commits:

Chengguang Xu (1):
      [dbb857f8d17c] common/rc: perform _require_metadata_journaling check on overlay base fs

Darrick J. Wong (1):
      [dc325ce8cafd] xfs: find libxfs api violations

Eric Whitney (1):
      [2931de473cc1] common/rc: ext4 doesn't support O_DIRECT with data journaling

Hou Tao (4):
      [976c9ca6561c] dmflakey: support multiple dm targets for a dm-flakey device
      [b237e01b1288] dmflakey: support error_writes feature for dm-flakey
      [20cb5f11991c] common/rc: factor out _scratch_xfs_[get|set]_sb_field
      [8f20e80747d9] xfs: test for umount hang caused by the pending dquota log item in AIL

Nikolay Borisov (1):
      [97575acd7495] generic/015: Change the test filesystem size to 101mb

Qu Wenruo (1):
      [3651c38e0b9c] filter: Introduce filter to filter out offset for xfs_io

Tuomas Tynkkynen (1):
      [ee55ddd38f01] fstests: Add 9p network filesystem support


Code Diffstat:

 check               |   2 +
 common/attr         |   4 +-
 common/config       |   9 +++
 common/dmflakey     |  31 +++++++++-
 common/filter       |  10 ++-
 common/fuzzy        |  33 ----------
 common/rc           |  46 +++++++++++++-
 common/xfs          |  47 ++++++++++++++
 tests/btrfs/140     |   9 ++-
 tests/btrfs/140.out |  70 ++++++++++-----------
 tests/btrfs/141     |   9 ++-
 tests/btrfs/141.out |  70 ++++++++++-----------
 tests/btrfs/142     |   9 ++-
 tests/btrfs/142.out |  70 ++++++++++-----------
 tests/btrfs/143     |   9 ++-
 tests/btrfs/143.out |  70 ++++++++++-----------
 tests/generic/015   |   6 +-
 tests/xfs/007       |   6 +-
 tests/xfs/098       |   4 +-
 tests/xfs/186       |   3 +-
 tests/xfs/199       |  13 ++--
 tests/xfs/307       |  11 +---
 tests/xfs/308       |  11 +---
 tests/xfs/339       |   6 +-
 tests/xfs/340       |   2 +-
 tests/xfs/437       |  56 +++++++++++++++++
 tests/xfs/437.out   |   2 +
 tests/xfs/438       | 174 ++++++++++++++++++++++++++++++++++++++++++++++++++++
 tests/xfs/438.out   |   2 +
 tests/xfs/group     |   2 +
 30 files changed, 564 insertions(+), 232 deletions(-)
--
Eryu Guan
eguan@redhat.com

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

                 reply	other threads:[~2018-01-14 15:42 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=5a5b7a46.097e630a.f6df2.94c0@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