From: "Theodore Tso" <tytso@mit.edu>
To: Jan Kara <jack@suse.cz>
Cc: Andreas Dilger <adilger@dilger.ca>,
Milos Nikic <nikic.milos@gmail.com>,
linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] jbd2: enforce power-of-two default revoke hash size at compile time
Date: Thu, 16 Apr 2026 07:54:35 -0400 [thread overview]
Message-ID: <20260416115435.GA52577@macsyma-wired.lan> (raw)
In-Reply-To: <gq6n6m75h47lcr2hvmtlun7revnyf3bx3aanndglbh6djmrjcp@jmxhl7kf7bwu>
On Thu, Apr 16, 2026 at 12:16:05PM +0200, Jan Kara wrote:
>
> Yes, I know. But there is already a runtime assertion in
> jbd2_journal_init_revoke() making sure the passed value is a power of two
> which is verifying also other callers that aren't using
> JOURNAL_REVOKE_DEFAULT_HASH value. I don't see a value in the *additional*
> BUILD_BUG_ON when we already have that runtime check.
... and if a developer doesn't run regression tests before bothering
the list with a patch... that's not a developer we want to cater to.
Milos, my recommended to workflow is to use kvm-xfstests[1], and just do:
% install-kconfig
% kbuild
% kvm-xfstests smoke
[1] https://github.com/tytso/xfstests-bld/blob/master/Documentation/kvm-quickstart.md
For a successful run, "kvm-xfstests smoke" will run take 15-20
minutes. In the case of screwing up the default power-of-two default
revoke hash size, "kvm-xfstests smoke" will report a failure in less
than a minute.
- Ted
prev parent reply other threads:[~2026-04-16 11:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-13 21:27 [PATCH] jbd2: enforce power-of-two default revoke hash size at compile time Milos Nikic
2026-04-14 12:59 ` Jan Kara
2026-04-16 1:35 ` Andreas Dilger
2026-04-16 10:16 ` Jan Kara
2026-04-16 11:54 ` Theodore Tso [this message]
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=20260416115435.GA52577@macsyma-wired.lan \
--to=tytso@mit.edu \
--cc=adilger@dilger.ca \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nikic.milos@gmail.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