From: Eryu Guan <guaneryu@gmail.com>
To: fstests@vger.kernel.org
Subject: [ANNOUNCE] fstests: master branch updated to 75bd80f900ea
Date: Sun, 27 Sep 2020 18:17:51 +0800 [thread overview]
Message-ID: <5f7066d2.1c69fb81.a8fa5.64fd@mx.google.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2505 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 mainly added IO_URING support to fsstress
and fsx, many thanks to Zorro Lang for doing this, also thanks to Brian Foster
for reviewing the patches!
There're also 3 new btrfs tests, which all should fail with latest kernel.
Thanks,
Eryu
The new head of the master branch is commit:
75bd80f900ea src/t_mmap_dio: do not build if !HAVE_AIO
New commits:
Eric Sandeen (1):
[75bd80f900ea] src/t_mmap_dio: do not build if !HAVE_AIO
Filipe Manana (3):
[03abb090754c] btrfs: test incremental send after a succession of rename and link operations
[e240c4a965a5] btrfs: test incremental send after swapping same file with two directories
[353bfccf5cdd] btrfs: test fstrim after doing a device replace
Johannes Thumshirn (2):
[63aee278f796] btrfs: remove stale test for alien devices from auto group
[6e723496c1bc] btrfs/125: remove constantly failing test from auto group
Pavel Reichl (1):
[bfe532d6e26c] xfs: Add test for too-small device with stripe geometry
Zorro Lang (6):
[57a18fcb244c] fsstress: add IO_URING read and write operations
[4cf0a1e57cdc] fsstress: reduce the number of events when io_setup
[7f9458a36f9b] fsstress: fix memory leak in do_aio_rw
[5fbda8d18375] fsx: introduce fsx_rw to combine aio_rw with general read and write
[f27875f08965] fsx: add IO_URING test
[823c491b2dca] generic/611: remove _supported_os line
Code Diffstat:
README | 4 +-
configure.ac | 1 +
include/builddefs.in | 1 +
ltp/Makefile | 5 ++
ltp/fsstress.c | 183 ++++++++++++++++++++++++++++++++++++++++++-------
ltp/fsx.c | 165 +++++++++++++++++++++++++++++++++++++++-----
m4/Makefile | 1 +
m4/package_liburing.m4 | 4 ++
src/Makefile | 3 +-
tests/btrfs/221 | 119 ++++++++++++++++++++++++++++++++
tests/btrfs/221.out | 6 ++
tests/btrfs/222 | 142 ++++++++++++++++++++++++++++++++++++++
tests/btrfs/222.out | 6 ++
tests/btrfs/223 | 71 +++++++++++++++++++
tests/btrfs/223.out | 7 ++
tests/btrfs/group | 7 +-
tests/generic/611 | 1 -
tests/xfs/260 | 51 ++++++++++++++
tests/xfs/260.out | 2 +
tests/xfs/group | 1 +
20 files changed, 733 insertions(+), 47 deletions(-)
--
Eryu Guan
guaneryu@gmail.com
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
reply other threads:[~2020-09-27 10: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=5f7066d2.1c69fb81.a8fa5.64fd@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