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 ab9b671c5549
Date: Sun, 08 Aug 2021 23:39:11 +0800	[thread overview]
Message-ID: <610ffaa3.1c69fb81.bcd0.708c@mx.google.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1956 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. And thanks to Darrick J. Wong, dmflakey tests now work
with xfs rt/log devices. dmerror support to rt/log devices is still on the way.

There're also two new tests, btrfs/244 and xfs/175, and btrfs/244 currently may
crash your v5.14-rc4 kernel, so it's marked as 'dangerous'. There're also two
bug fixes, one fixes a regression introduced by last update, one fixes
SEEK_DATA/SEEK_HOLE behavior on NFSv4.2.

And there're still remaining review backlogs:

- new xfs tests from Darrick
- Extend idmapped mount testsuite from Christian Brauner

It's really appreciated if anyone could help review above patches!

Thanks,
Eryu

The new head of the master branch is commit:

ab9b671c5549 dmerror: export configuration so that subprograms don't have to reinit

New commits:

Amir Goldstein (1):
      [de1196dcd9b6] overlay/078: Fix cleanup with unpatched kernel

Darrick J. Wong (2):
      [9c1f3149271f] dmflakey: support external log and realtime devices
      [ab9b671c5549] dmerror: export configuration so that subprograms don't have to reinit

Jeffle Xu (1):
      [4b7ea02dc05b] common/rc: only force nfs4.2 non-default SEEK_HOLE behaviour

Qu Wenruo (1):
      [da693469b7a1] btrfs: verify the behavior of deleting non-existing device

Zorro Lang (1):
      [c124d3a3116d] xfs: quota state command should report upg grace times separately


Code Diffstat:

 common/dmerror      |   8 ++--
 common/dmflakey     | 106 ++++++++++++++++++++++++++++++++++++++++++++++++++--
 common/rc           |   8 ++--
 src/dmerror         |  13 +++----
 tests/btrfs/244     |  47 +++++++++++++++++++++++
 tests/btrfs/244.out |   2 +
 tests/overlay/078   |   3 ++
 tests/xfs/175       |  37 ++++++++++++++++++
 tests/xfs/175.out   |  21 +++++++++++
 9 files changed, 227 insertions(+), 18 deletions(-)
--
Eryu Guan
guaneryu@gmail.com

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

                 reply	other threads:[~2021-08-08 15:39 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=610ffaa3.1c69fb81.bcd0.708c@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