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 10f6b23121ea
Date: Sun, 18 Jul 2021 23:25:12 +0800	[thread overview]
Message-ID: <60f447dc.1c69fb81.4d473.788f@mx.google.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 2721 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 two new btrfs tests, and btrfs/243 currently
fails with v5.13 kernel (I haven't tried v5.14-rc1 as I couldn't boot my vm due
to NULL pointer dereference, but the proposed fix hasn't landed upstream, so it
should fail there as well).

Others are random bug fixes as usual, most of them are contributed by
Darrick J. Wong and reviewed by Allison Henderson, thank you both!

Thanks,
Eryu

The new head of the master branch is commit:

10f6b23121ea generic/019: don't dump cores when fio/fsstress hit io errors

New commits:

Anand Jain (1):
      [2226eece67ba] btrfs: test case to fstrim on a degraded filesystem

Darrick J. Wong (7):
      [0de642617f18] xfs/172: disable test when file writes don't use delayed allocation
      [75c9b616fc84] shared/298: fix random deletion when filenames contain spaces
      [ffaba0eb3fc1] dmthin: erase the metadata device properly before starting
      [473cf6fb2e5e] check: run _check_filesystems in an OOM-happy subshell
      [d72d1ba33055] xfs/084: fix test program status collection and processing
      [272940ff28e9] generic/371: disable speculative preallocation regressions on XFS
      [10f6b23121ea] generic/019: don't dump cores when fio/fsstress hit io errors

Dave Chinner (1):
      [391b0b0908da] generic/459: catch mount failure

Filipe Manana (1):
      [8ae8a045b54d] btrfs: test fsync after increasing file size with truncate

Matthew Wilcox (1):
      [6aa7a5c71497] src/seek_sanity_test: test seeks from LLONG_MIN

Naohiro Aota (1):
      [99baa0ade4e1] fstests: install btrfs_crc32c_forged_name.py

Pavel Reichl (1):
      [6fc0bd027a74] generic/{453,454}: Don't run for FSs restricting names

Theodore Ts'o (1):
      [3ff9e88c096a] ext4/048: skip test of filename wipe if journal checkpoint is not supported


Code Diffstat:

 check                  | 24 +++++++++----
 common/dmthin          |  8 +++--
 common/rc              | 13 +++++++
 src/Makefile           |  5 ++-
 src/seek_sanity_test.c |  4 +++
 tests/btrfs/242        | 49 ++++++++++++++++++++++++++
 tests/btrfs/242.out    |  7 ++++
 tests/btrfs/243        | 93 ++++++++++++++++++++++++++++++++++++++++++++++++++
 tests/btrfs/243.out    | 15 ++++++++
 tests/ext4/048         |  8 +++++
 tests/generic/019      |  3 ++
 tests/generic/371      |  8 +++++
 tests/generic/453      |  1 +
 tests/generic/454      |  1 +
 tests/generic/459      |  4 ++-
 tests/shared/298       |  2 +-
 tests/xfs/084          |  8 +++--
 tests/xfs/172          | 30 +++++++++++++++-
 18 files changed, 268 insertions(+), 15 deletions(-)
--
Eryu Guan
guaneryu@gmail.com

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

                 reply	other threads:[~2021-07-18 15:25 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=60f447dc.1c69fb81.4d473.788f@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