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 ea817058b0bc
Date: Mon, 25 Sep 2017 01:24:32 +0800	[thread overview]
Message-ID: <59c7ea52.c106620a.572ea.29c0@mx.google.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1319 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 is a normal bug fixes and improvements update,
with only one new test for XFS, and I didn't see any new failures introduced.

Thanks,
Eryu

The new head of the master branch is commit:

ea817058b0bc xfs: Add test for CVE-2017-14340

New commits:

Amir Goldstein (3):
      [de5925929857] overlay/038: fix impure xattr test
      [5052c432b558] overlay/014: correct comment relating to workdir reuse
      [a21f34f87f8e] overlay/031: fix test with inodes index enabled

Andreas Gruenbacher (1):
      [e04905eba73a] common/rc: Improve gfs2 support

Christoph Hellwig (1):
      [b88444413a0f] xfs/310: relax extent count check

Richard Wareing (1):
      [ea817058b0bc] xfs: Add test for CVE-2017-14340

xiao yang (1):
      [7ef45e8a3856] xfs/115: add missing 115 into group file


Code Diffstat:

 common/rc         |  6 ++++
 tests/overlay/014 |  7 ++---
 tests/overlay/031 | 23 ++++++++++-----
 tests/overlay/038 | 12 ++++----
 tests/xfs/310     |  5 ++--
 tests/xfs/431     | 84 +++++++++++++++++++++++++++++++++++++++++++++++++++++++
 tests/xfs/431.out |  3 ++
 tests/xfs/group   |  2 ++
 8 files changed, 123 insertions(+), 19 deletions(-)
--
Eryu Guan
eguan@redhat.com

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

                 reply	other threads:[~2017-09-24 17: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=59c7ea52.c106620a.572ea.29c0@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