From: "Theodore Tso" <tytso@mit.edu>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: Ojaswin Mujoo <ojaswin@linux.ibm.com>,
Zorro Lang <zlang@redhat.com>,
fstests@vger.kernel.org, fdmanana@suse.com,
ritesh.list@gmail.com, naohiro.aota@wdc.com, wqu@suse.com,
Disha Goel <disgoel@linux.ibm.com>,
linux-ext4 <linux-ext4@vger.kernel.org>
Subject: Re: [PATCH 4/6] generic/765: Ignore mkfs warning
Date: Mon, 13 Apr 2026 16:42:15 -0400 [thread overview]
Message-ID: <20260413204215.GA5461@macsyma-wired.lan> (raw)
In-Reply-To: <20260413162120.GV6212@frogsfrogsfrogs>
> > > > > 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.
You could also suppress the warnings using the -q option, for example:
mke2fs -Fq -t ext4 -O bigalloc,quota -b 4096 -C 131072 /tmp/foo.img 4G
> > Futher, mke2fs has multiple instances where we print warnings to stderr,
> > should we go and fix all of them as well?
>
> "stderr" meaning "standard error", I'd say that errors are anything that
> prohibits the format from completing, and only errors should go there.
Sure, I'll accept those changes. But adding -q will allow the test to
pass using older versions of e2fsprogs, while still allowing stderr to
go out the expected output.
- Ted
next prev parent reply other threads:[~2026-04-13 20:43 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 [this message]
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
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=20260413204215.GA5461@macsyma-wired.lan \
--to=tytso@mit.edu \
--cc=disgoel@linux.ibm.com \
--cc=djwong@kernel.org \
--cc=fdmanana@suse.com \
--cc=fstests@vger.kernel.org \
--cc=linux-ext4@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 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.