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 ac23422a8c7d
Date: Sun, 15 Nov 2020 17:13:14 +0800	[thread overview]
Message-ID: <5fb0f12e.1c69fb81.8794b.fb70@mx.google.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 2043 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. Thanks to Zorro Lang, there're two new tests that
execrise io_uring based fsx tests, one of them just triggered one io_uring bug
in kernel (and fixed in latest kernel). Also, there's a new test that makes
sure st_blocks is never zero while writing into a file, which currently fails
on btrfs.

Other commits are random fixes, and fsstress and fsx get rid of some build
warnings.

Thanks,
Eryu

The new head of the master branch is commit:

ac23422a8c7d generic: fsx IO_URING direct-IO soak tests

New commits:

Darrick J. Wong (3):
      [4f8a21fa8d32] fsx: fix strncpy usage error
      [808f39a416c9] fsstress: stop using attr_set
      [0743230c3602] fsstress: remove attr_remove

Eric Biggers (1):
      [609bb3562241] fscrypt-crypt-util: fix maximum IV size

Filipe Manana (1):
      [7a327ad2f4da] generic: test for non-zero used blocks while writing into a file

Xiao Yang (1):
      [bd3353b0d4d9] generic/426: Remove unused opt variable in create_test_files()

Zorro Lang (3):
      [6f87118198dd] src/feature: add IO_URING feature checking
      [c3eb99947700] generic: fsx IO_URING soak tests
      [ac23422a8c7d] generic: fsx IO_URING direct-IO soak tests


Code Diffstat:

 common/rc                | 16 +++++++++
 ltp/fsstress.c           | 29 ++++++++++-------
 ltp/fsx.c                |  5 ++-
 src/Makefile             |  4 +++
 src/feature.c            | 41 +++++++++++++++++++++--
 src/fscrypt-crypt-util.c |  7 ++--
 tests/generic/426        |  1 -
 tests/generic/615        | 84 ++++++++++++++++++++++++++++++++++++++++++++++++
 tests/generic/615.out    |  3 ++
 tests/generic/616        | 58 +++++++++++++++++++++++++++++++++
 tests/generic/616.out    |  2 ++
 tests/generic/617        | 64 ++++++++++++++++++++++++++++++++++++
 tests/generic/617.out    |  2 ++
 tests/generic/group      |  3 ++
 14 files changed, 298 insertions(+), 21 deletions(-)
--
Eryu Guan
guaneryu@gmail.com

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

                 reply	other threads:[~2020-11-15  9:13 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=5fb0f12e.1c69fb81.8794b.fb70@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