From: Dhruva G <goledhruva@gmail.com>
To: fstests@vger.kernel.org
Cc: Anand Jain <asj@kernel.org>, Filipe Manana <fdmanana@suse.com>,
Zorro Lang <zlang@kernel.org>,
linux-btrfs@vger.kernel.org, quwenruo.btrfs@gmx.com
Subject: [PATCH 0/3] btrfs: add NOCOMPRESS defrag regression coverage
Date: Mon, 12 Oct 2026 01:04:33 +0530 [thread overview]
Message-ID: <51964611-cd9b-48ad-b6ca-45373a96f64a@gmail.com> (raw)
Add regression coverage for BTRFS_DEFRAG_RANGE_NOCOMPRESS, introduced by
kernel commit 009b2056cb25 ("btrfs: defrag: add flag to force
no-compression").
The series checks bounded conversion and EOF handling, preservation of
holes and preallocated extents, and inline extent eligibility and short
EOF tails. FIEMAP assertions inspect every overlapping extent and require
complete range coverage. File contents, sizes, and extent state are
checked again after remounting.
Patch 1 adds the shared helpers and a small raw-ioctl program used for
feature probing and errno checks. Patches 2 and 3 add sparse-layout and
inline/tail coverage. The tests require 4K sectors and btrfs-progs with
--nocomp support; unsupported configurations skip.
Tested on an x86_64 QEMU/KVM guest with:
Linux 7.3.0-rc3-next-20260918-btrfs-lab
btrfs-progs v7.1
4K Btrfs scratch sectors
Dhruva Gole (3):
btrfs: exercise NOCOMPRESS range and EOF handling
btrfs: check NOCOMPRESS preserves holes and preallocation
btrfs: cover NOCOMPRESS inline eligibility and short tails
.gitignore | 1 +
common/btrfs_nocomp | 134 ++++++++++++++++++++++++++++++++++++++
src/Makefile | 2 +-
src/btrfs_defrag_nocomp.c | 63 ++++++++++++++++++
tests/btrfs/355 | 80 +++++++++++++++++++++++
tests/btrfs/355.out | 2 +
tests/btrfs/356 | 71 ++++++++++++++++++++
tests/btrfs/356.out | 2 +
tests/btrfs/357 | 59 +++++++++++++++++
tests/btrfs/357.out | 2 +
10 files changed, 415 insertions(+), 1 deletion(-)
create mode 100644 common/btrfs_nocomp
create mode 100644 src/btrfs_defrag_nocomp.c
create mode 100755 tests/btrfs/355
create mode 100644 tests/btrfs/355.out
create mode 100755 tests/btrfs/356
create mode 100644 tests/btrfs/356.out
create mode 100755 tests/btrfs/357
create mode 100644 tests/btrfs/357.out
base-commit: 56c410ad0f69da5b13c5807bc47b4876dcfa02b2
--
2.43.0
reply other threads:[~2026-10-11 19:34 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=51964611-cd9b-48ad-b6ca-45373a96f64a@gmail.com \
--to=goledhruva@gmail.com \
--cc=asj@kernel.org \
--cc=fdmanana@suse.com \
--cc=fstests@vger.kernel.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=quwenruo.btrfs@gmx.com \
--cc=zlang@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