From: Anand Jain <anand.jain@oracle.com>
To: fstests@vger.kernel.org
Cc: linux-btrfs@vger.kernel.org
Subject: [GIT PULL] fstests: btrfs changes staged-20250109
Date: Thu, 9 Jan 2025 23:09:14 +0800 [thread overview]
Message-ID: <20250109150955.109775-1-anand.jain@oracle.com> (raw)
In-Reply-To: <c4847cd94f86bd98fc563f112e177b317dc21111.1732102551.git.anand.jain@oracle.com>
(ml emailid fixed)
Zorro,
Please pull these small changes; they have been reviewed and tested.
Thank you.
The following changes since commit d862cf27d1b44de3e3d0b8380d22ef43b308ca32:
generic/530: only use xfs-specific mkfs options when testing on xfs (2024-12-19 18:18:47 +0800)
are available in the Git repository at:
https://github.com/asj/fstests.git staged-20250109
for you to fetch changes up to 73e44e1ba7bf072a9e4f77bc3ac6a60eebe0102a:
btrfs: test cycle mounting a filesystem right after enabling simple quotas (2025-01-09 11:00:37 +0800)
----------------------------------------------------------------
Filipe Manana (1):
btrfs: test cycle mounting a filesystem right after enabling simple quotas
Mark Harmstone (2):
configure: use pkg-config to find liburing
btrfs: add test for encoded reads
Qu Wenruo (1):
btrfs/326: update _fixed_by_kernel_commit
.gitignore | 2 +
VERSION | 8 +-
common/btrfs | 32 ++++++
m4/package_globals.m4 | 4 +-
m4/package_liburing.m4 | 8 +-
release.sh | 2 +-
src/Makefile | 1 +
src/btrfs_encoded_read.c | 195 +++++++++++++++++++++++++++++++++
src/btrfs_encoded_write.c | 226 ++++++++++++++++++++++++++++++++++++++
src/feature.c | 4 +-
src/vfs/idmapped-mounts.c | 6 +-
src/vfs/idmapped-mounts.h | 2 +-
src/vfs/tmpfs-idmapped-mounts.c | 6 +-
src/vfs/utils.c | 4 +-
src/vfs/utils.h | 6 +-
src/vfs/vfstest.c | 6 +-
tests/btrfs/326 | 7 +-
tests/btrfs/328 | 31 ++++++
tests/btrfs/328.out | 2 +
tests/btrfs/333 | 233 ++++++++++++++++++++++++++++++++++++++++
tests/btrfs/333.out | 2 +
21 files changed, 761 insertions(+), 26 deletions(-)
create mode 100644 src/btrfs_encoded_read.c
create mode 100644 src/btrfs_encoded_write.c
create mode 100755 tests/btrfs/328
create mode 100644 tests/btrfs/328.out
create mode 100755 tests/btrfs/333
create mode 100644 tests/btrfs/333.out
prev parent reply other threads:[~2025-01-09 15:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-20 11:40 [PATCH] fstests: fix blksize_t printf format warnings across architectures Anand Jain
2024-11-20 16:28 ` Darrick J. Wong
2024-11-21 2:04 ` Anand Jain
2024-11-20 22:06 ` Qu Wenruo
2024-11-20 22:21 ` Darrick J. Wong
2024-11-20 23:10 ` Qu Wenruo
2025-01-09 15:09 ` Anand Jain [this message]
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=20250109150955.109775-1-anand.jain@oracle.com \
--to=anand.jain@oracle.com \
--cc=fstests@vger.kernel.org \
--cc=linux-btrfs@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