From: "Theodore Ts'o" <tytso@mit.edu>
To: Ojaswin Mujoo <ojaswin@linux.ibm.com>
Cc: Zorro Lang <zlang@redhat.com>,
fstests@vger.kernel.org, Ritesh Harjani <ritesh.list@gmail.com>,
djwong@kernel.org, john.g.garry@oracle.com
Subject: Re: [PATCH v2 02/13] common/rc: Fix fsx for ext4 with bigalloc
Date: Thu, 26 Jun 2025 09:32:39 -0400 [thread overview]
Message-ID: <20250626133239.GA7524@mit.edu> (raw)
In-Reply-To: <4f09b788f506223c9631479d0318be1e1ba5883c.1750924903.git.ojaswin@linux.ibm.com>
On Thu, Jun 26, 2025 at 05:28:53PM +0530, Ojaswin Mujoo wrote:
> This is achieved by defining a new function _set_default_fsx_avoid
> called via run_fsx helper. This can be used to selectively disable
> fsx options based on the configuration.
> +_set_default_fsx_avoid() {
> + case "$FSTYP" in
> + "ext4")
> + if [[ "$MKFS_OPTIONS" =~ bigalloc ]]; then
> + export FSX_AVOID+=" -I -C"
> + fi
> + ;;
This assumes that MKFS_OPTIONS reflects the file system features
enabled on the file system. That's true by definition for the scratch
fs, but it's not necessarily true for the test fs. At least in
theory, someone could run fstests without a scrach device, and then
MKFS_OPTION?S might not be set.
I'm not sure that we care; is this something that we make assumptions
in other tests?
- Ted
next prev parent reply other threads:[~2025-06-26 13:33 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-26 11:58 [PATCH v2 00/13] Add more tests for multi fs block atomic writes Ojaswin Mujoo
2025-06-26 11:58 ` [PATCH v2 01/13] common/rc: Add _min() and _max() helpers Ojaswin Mujoo
2025-06-26 11:58 ` [PATCH v2 02/13] common/rc: Fix fsx for ext4 with bigalloc Ojaswin Mujoo
2025-06-26 13:32 ` Theodore Ts'o [this message]
2025-06-30 15:28 ` Darrick J. Wong
2025-07-01 6:26 ` Ojaswin Mujoo
2025-07-02 15:13 ` Darrick J. Wong
2025-06-26 11:58 ` [PATCH v2 03/13] common/rc: Add a helper to run fsx on a given file Ojaswin Mujoo
2025-06-26 11:58 ` [PATCH v2 04/13] ltp/fsx.c: Add atomic writes support to fsx Ojaswin Mujoo
2025-06-26 11:58 ` [PATCH v2 05/13] generic/1226: Add atomic write test using fio crc check verifier Ojaswin Mujoo
2025-06-27 14:09 ` John Garry
2025-07-01 16:18 ` Ojaswin Mujoo
2025-07-02 7:46 ` John Garry
2025-07-03 6:42 ` Ojaswin Mujoo
2025-07-03 16:26 ` John Garry
2025-07-04 14:35 ` Ojaswin Mujoo
2025-07-04 15:23 ` Ojaswin Mujoo
2025-07-07 8:18 ` John Garry
2025-07-08 6:50 ` Ojaswin Mujoo
2025-07-08 11:11 ` John Garry
2025-07-08 12:01 ` Ojaswin Mujoo
2025-07-08 12:34 ` John Garry
2025-07-11 10:39 ` Ojaswin Mujoo
2025-07-11 10:51 ` John Garry
2025-07-11 18:16 ` Ojaswin Mujoo
2025-07-07 8:02 ` John Garry
2025-06-26 11:58 ` [PATCH v2 06/13] generic/1227: Add atomic write test using fio verify on file mixed mappings Ojaswin Mujoo
2025-06-27 14:48 ` John Garry
2025-06-26 11:58 ` [PATCH v2 07/13] generic/1228: Add atomic write multi-fsblock O_[D]SYNC tests Ojaswin Mujoo
2025-06-26 11:58 ` [PATCH v2 08/13] generic/1229: Stress fsx with atomic writes enabled Ojaswin Mujoo
2025-06-26 11:59 ` [PATCH v2 09/13] generic/1230: Add sudden shutdown tests for multi block atomic writes Ojaswin Mujoo
2025-06-27 16:11 ` John Garry
2025-07-01 6:34 ` Ojaswin Mujoo
2025-06-26 11:59 ` [PATCH v2 10/13] ext4/061: Atomic writes stress test for bigalloc using fio crc verifier Ojaswin Mujoo
2025-06-26 11:59 ` [PATCH v2 11/13] ext4/062: Atomic writes test for bigalloc using fio crc verifier on multiple files Ojaswin Mujoo
2025-06-26 11:59 ` [PATCH v2 12/13] ext4/063: Atomic write test for extent split across leaf nodes Ojaswin Mujoo
2025-06-26 11:59 ` [PATCH v2 13/13] ext4/064: Add atomic write tests for journal credit calculation Ojaswin Mujoo
2025-06-27 13:56 ` [PATCH v2 00/13] Add more tests for multi fs block atomic writes John Garry
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=20250626133239.GA7524@mit.edu \
--to=tytso@mit.edu \
--cc=djwong@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=john.g.garry@oracle.com \
--cc=ojaswin@linux.ibm.com \
--cc=ritesh.list@gmail.com \
--cc=zlang@redhat.com \
/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