From: Disha Goel <disgoel@linux.ibm.com>
To: Ojaswin Mujoo <ojaswin@linux.ibm.com>,
Zorro Lang <zlang@redhat.com>,
fstests@vger.kernel.org
Cc: djwong@kernel.org, fdmanana@suse.com, ritesh.list@gmail.com,
naohiro.aota@wdc.com, wqu@suse.com
Subject: Re: [PATCH 4/6] generic/765: Ignore mkfs warning
Date: Tue, 14 Apr 2026 15:32:03 +0530 [thread overview]
Message-ID: <a0e7e21d-04b7-4bd2-b851-879d86e557f8@linux.ibm.com> (raw)
In-Reply-To: <afee4fedcc9b3685df0e05800d82b88d27f977f8.1775802601.git.ojaswin@linux.ibm.com>
On 10/04/26 12:06 pm, Ojaswin Mujoo wrote:
> This test validates atomic writes for all possible block sizes. In ext4, for
> smaller block sizes with configurations like:
>
> export MKFS_OPTIONS="-O bigalloc,quota -b 65536 -C 131072"
>
> The output can get corrupted with warnings like below because clustersize
> more than 16xbs is experimental:
>
> + 16 times the block size is considered experimental
>
> Hence pipe these to seqres.full to avoid false negatives.
>
> Reported-by: Disha Goel <disgoel@linux.ibm.com>
> Signed-off-by: Ojaswin Mujoo <ojaswin@linux.ibm.com>
I've tested this patch and the test now runs cleanly without false
negatives from the experimental configuration warnings.
Tested-by: Disha Goel <disgoel@linux.ibm.com>
> ---
> tests/generic/765 | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/tests/generic/765 b/tests/generic/765
> index 09be53db..b7cc70f1 100755
> --- a/tests/generic/765
> +++ b/tests/generic/765
> @@ -64,7 +64,8 @@ test_atomic_writes()
> local bsize=$1
>
> get_mkfs_opts $bsize
> - _scratch_mkfs $mkfs_opts >> $seqres.full
> + _scratch_mkfs $mkfs_opts &>> $seqres.full || \
> + echo "mkfs $mkfs_opts failed"
> _scratch_mount
>
> test "$FSTYP" = "xfs" && _xfs_force_bdev data $SCRATCH_MNT
--
Regards,
Disha
next prev parent reply other threads:[~2026-04-14 10:02 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-10 6:36 [PATCH v2 0/6] Atomic write test fixes & refactoring Ojaswin Mujoo
2026-04-10 6:36 ` [PATCH 1/6] ext4/061,062: Minor fixes and refactoring Ojaswin Mujoo
2026-04-14 9:52 ` Disha Goel
2026-04-10 6:36 ` [PATCH 2/6] common/rc: Add _sysfs_queue_path helper with partition support Ojaswin Mujoo
2026-04-10 16:50 ` Darrick J. Wong
2026-04-10 6:36 ` [PATCH 3/6] generic/765: Fix sysfs queue path for nvme partitions Ojaswin Mujoo
2026-04-10 16:50 ` Darrick J. Wong
2026-04-14 9:58 ` Disha Goel
2026-04-10 6:36 ` [PATCH 4/6] generic/765: Ignore mkfs warning Ojaswin Mujoo
2026-04-10 16:54 ` Darrick J. Wong
2026-04-12 17:08 ` Ojaswin Mujoo
2026-04-13 9:04 ` Ojaswin Mujoo
2026-04-13 16:21 ` Darrick J. Wong
2026-04-13 20:42 ` Theodore Tso
2026-04-13 23:28 ` Darrick J. Wong
2026-04-15 18:52 ` Ojaswin Mujoo
2026-04-16 15:55 ` Zorro Lang
2026-04-12 19:23 ` Zorro Lang
2026-04-13 9:09 ` Ojaswin Mujoo
2026-04-14 10:02 ` Disha Goel [this message]
2026-04-10 6:36 ` [PATCH 5/6] generic/775: Fix an infinite loop due to variable name clash Ojaswin Mujoo
2026-04-10 16:51 ` Darrick J. Wong
2026-04-14 10:05 ` Disha Goel
2026-04-10 6:36 ` [PATCH 6/6] treewide: Use _sysfs_queue_path helper in all queue access locations Ojaswin Mujoo
2026-04-10 16:52 ` Darrick J. Wong
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=a0e7e21d-04b7-4bd2-b851-879d86e557f8@linux.ibm.com \
--to=disgoel@linux.ibm.com \
--cc=djwong@kernel.org \
--cc=fdmanana@suse.com \
--cc=fstests@vger.kernel.org \
--cc=naohiro.aota@wdc.com \
--cc=ojaswin@linux.ibm.com \
--cc=ritesh.list@gmail.com \
--cc=wqu@suse.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