FS/XFS testing framework
 help / color / mirror / Atom feed
From: Jeff Layton <jlayton@kernel.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: Zorro Lang <zlang@kernel.org>,
	fstests@vger.kernel.org,  linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH RFC fstests] generic: add a test for multigrain timestamps
Date: Wed, 28 Oct 2026 13:20:24 -0400	[thread overview]
Message-ID: <3a5b0778c77df7cce94bf9fce974b1bf1dfb6324.camel@kernel.org> (raw)
In-Reply-To: <auIavey7CFq_l38s@infradead.org>

On Wed, 2026-10-28 at 08:54 -0700, Christoph Hellwig wrote:
> On Tue, Oct 27, 2026 at 09:58:50AM -0400, Jeff Layton wrote:
> > Ensure that the mtime and ctime apparently change, even when there are
> > multiple writes in quick succession. Since this is opt-in for in-kernel
> > filesystems and there is no way to test for this feature in userland,
> > limit it to just ext4, f2fs, btrfs, tmpfs and xfs for now.
> > 
> > Signed-off-by: Jeff Layton <jlayton@kernel.org>
> > ---
> > I'd like to start testing this to make sure it doesn't break, but it's
> > not universally supported on all filesystems. Is an explicit allowlist
> > like this the right approach?
> 
> Can we please expose the fact that multi-grain timestamp are supported
> from the kernel?  This seems like it would be just one bit we'd need
> in sttx or something similar.

I'd been resisting that, but maybe it's a good idea. I'll see what I
can come up with. We can probably just add a flag to stx_attributes?
-- 
Jeff Layton <jlayton@kernel.org>

  reply	other threads:[~2026-10-28 17:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-27 13:58 [PATCH RFC fstests] generic: add a test for multigrain timestamps Jeff Layton
2026-10-28 15:54 ` Christoph Hellwig
2026-10-28 17:20   ` Jeff Layton [this message]
2026-10-29 12:02     ` Christoph Hellwig

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=3a5b0778c77df7cce94bf9fce974b1bf1dfb6324.camel@kernel.org \
    --to=jlayton@kernel.org \
    --cc=fstests@vger.kernel.org \
    --cc=hch@infradead.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=zlang@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox