All of lore.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 ab3df57e8659
Date: Sun, 11 Oct 2020 19:17:06 +0800	[thread overview]
Message-ID: <5f82e9b5.1c69fb81.8c00a.3b4e@mx.google.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 2431 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 pulls in the f2fs compression+encryption
test from Eric Biggers. There're also two new tests, one generic test and one
xfs test. Note that the new xfs/521 may crash your kernel when XFS_DEBUG is on.

Thanks,
Eryu

The new head of the master branch is commit:

ab3df57e8659 generic/611: Use _getfattr instead of GETFATTR_PROG

New commits:

Anand Jain (1):
      [65a20890998e] btrfs/064: add a comment to the test case header

Darrick J. Wong (2):
      [5f35d3df8a14] xfs/194: actually check if we got the desired block size before proceeding
      [6df280a68476] xfs: test running growfs on the realtime volume

Eric Biggers (5):
      [fa650493ef9f] fscrypt-crypt-util: clean up parsing --block-size and --inode-number
      [65cd8e8a8e81] fscrypt-crypt-util: fix IV incrementing for --iv-ino-lblk-32
      [300cd3558f43] fscrypt-crypt-util: add --block-number option
      [4057f495d572] common/f2fs: add _require_scratch_f2fs_compression()
      [8b28dae4ac8c] f2fs: verify ciphertext of compressed+encrypted file

Eric Sandeen (1):
      [b3170bfe8da1] generic: test reflinked file corruption after short COW

Vladimir Zapolskiy (1):
      [fce0f68a946f] generic/120: add the test to atime test group

Xiao Yang (2):
      [4616ec0a9df2] overlay/071: Fix undefined OVL_BASE_SCRATCH_DIR
      [72a84addd227] overlay/071: Don't compare inode numbers in lower overlay and nested overlay

Yang Xu (1):
      [ab3df57e8659] generic/611: Use _getfattr instead of GETFATTR_PROG


Code Diffstat:

 common/config            |   1 +
 common/f2fs              |  27 ++++++
 src/fscrypt-crypt-util.c |  98 ++++++++++++++-------
 tests/btrfs/064          |  10 ++-
 tests/f2fs/002           | 217 +++++++++++++++++++++++++++++++++++++++++++++++
 tests/f2fs/002.out       |  21 +++++
 tests/f2fs/group         |   1 +
 tests/generic/611        |   2 +-
 tests/generic/611.out    |   2 +-
 tests/generic/612        |  85 +++++++++++++++++++
 tests/generic/612.out    |  18 ++++
 tests/generic/group      |   3 +-
 tests/overlay/071        |  12 +--
 tests/xfs/194            |   3 +
 tests/xfs/521            |  82 ++++++++++++++++++
 tests/xfs/521.out        |  10 +++
 tests/xfs/group          |   1 +
 17 files changed, 548 insertions(+), 45 deletions(-)
--
Eryu Guan
guaneryu@gmail.com

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

                 reply	other threads:[~2020-10-11 11:17 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=5f82e9b5.1c69fb81.8c00a.3b4e@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.