From: Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>
To: linux-btrfs@vger.kernel.org
Cc: David Sterba <dsterba@suse.com>
Subject: [bug report] fstests failures at btrfs/003 and other test cases
Date: Sat, 9 May 2026 16:45:55 +0200 [thread overview]
Message-ID: <af9EHC5b-aBdr1zn@shinmob> (raw)
Hi David and all,
I found btrfs/003 and other test cases of fstests fail with the latest btrfs-
progs at the devel branch tip. The message "mkfs failed" is observed at the
failures [1]. I bisected and found the btrfs-progs commit below triggers the
failure.
ec8324cc4b8b ("btrfs-progs: help: adjust alignment of text")
This commit modified the help message of mkfs.btrfs command.
I found fstests checks the help message and greps with the pattern
"[[:space:]]-f[[:space:]|,]" in set_mkfs_prog_path_with_opts() [2]. The grep
succeeds before the commit, since it had spaces before "-f".
$ mkfs.btrfs --help |& grep -e "--force"
-f, --force force overwrite of existing filesystem
However, it fails to after the commit, since there is no space before "-f".
$ mkfs.btrfs --help |& grep -e "--force"
-f, --force force overwrite of existing filesystem
Then, fstests no longer adds -f option to not add $MKFS_BTRFS_PROGS.
Is this a known failure? If not, actions for fix will be appreciated.
[1]
$ sudo ./check btrfs/003
FSTYP -- btrfs
PLATFORM -- Linux/x86_64 redsun115 7.1.0-rc2-kts-btrfs #1 SMP PREEMPT_DYNAMIC Sat May 9 03:03:55 JST 2026
MKFS_OPTIONS -- -f /dev/nullb1
MOUNT_OPTIONS -- -o enospc_debug -o context=system_u:object_r:root_t:s0 /dev/nullb1 /var/kts/scratch
btrfs/003 55s ... [failed, exit status 1]- output mismatch (see /home/kts/kernel-test-suite/src/xfstests/results//btrfs/003.out.bad)
--- tests/btrfs/003.out 2026-05-09 03:07:52.952213772 +0900
+++ /home/kts/kernel-test-suite/src/xfstests/results//btrfs/003.out.bad 2026-05-09 23:32:17.595751435 +0900
@@ -1,2 +1,3 @@
QA output created by 003
-Silence is golden
+mkfs failed
+(see /home/kts/kernel-test-suite/src/xfstests/results//btrfs/003.full for details)
...
(Run 'diff -u /home/kts/kernel-test-suite/src/xfstests/tests/btrfs/003.out /home/kts/kernel-test-suite/src/xfstests/results//btrfs/003.out.bad' to see the entire diff)
Ran: btrfs/003
Failures: btrfs/003
Failed 1 of 1 tests
[2] https://git.kernel.org/pub/scm/fs/xfs/xfstests-dev.git/tree/common/config?h=for-next#n106
next reply other threads:[~2026-05-09 14:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-09 14:45 Shin'ichiro Kawasaki [this message]
2026-05-09 23:55 ` [bug report] fstests failures at btrfs/003 and other test cases Qu Wenruo
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=af9EHC5b-aBdr1zn@shinmob \
--to=shinichiro.kawasaki@wdc.com \
--cc=dsterba@suse.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.