public inbox for fstests@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Jeff Layton <jlayton@kernel.org>
Cc: fstests@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	Zorro Lang <zlang@redhat.com>,
	Christian Brauner <brauner@kernel.org>
Subject: Re: [PATCH fstests v3 3/3] generic: add tests for file delegations
Date: Mon, 5 Jan 2026 22:28:27 -0800	[thread overview]
Message-ID: <aVyriyPD8x8oJUo-@infradead.org> (raw)
In-Reply-To: <20251203-dir-deleg-v3-3-be55fbf2ad53@kernel.org>

On Wed, Dec 03, 2025 at 10:43:09AM -0500, Jeff Layton wrote:
> Mostly the same ones as leases, but some additional tests to validate
> that they are broken on metadata changes.

Under what conditions is this test supposed to actually work?  It seems
to consistently fail for me even with latest mainline, which is a bit
annoying.


  parent reply	other threads:[~2026-01-06  6:28 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-03 15:43 [PATCH fstests v3 0/3] generic: new testcases for delegation support Jeff Layton
2025-12-03 15:43 ` [PATCH fstests v3 1/3] common/rc: clean up after the _require_test_fcntl_setlease() test Jeff Layton
2025-12-05 17:14   ` Zorro Lang
2025-12-03 15:43 ` [PATCH fstests v3 2/3] generic: add tests for directory delegations Jeff Layton
2025-12-05 17:15   ` Zorro Lang
2025-12-03 15:43 ` [PATCH fstests v3 3/3] generic: add tests for file delegations Jeff Layton
2025-12-05 17:25   ` Zorro Lang
2025-12-06 18:35     ` Jeff Layton
2025-12-16 17:13       ` Darrick J. Wong
2025-12-16 17:57         ` Jeff Layton
2025-12-16 18:22           ` Darrick J. Wong
2026-01-06  6:28   ` Christoph Hellwig [this message]
2026-01-06 11:09     ` Jeff Layton
2026-01-07  5:58       ` Christoph Hellwig
2026-01-07 13:03         ` Jeff Layton

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=aVyriyPD8x8oJUo-@infradead.org \
    --to=hch@infradead.org \
    --cc=brauner@kernel.org \
    --cc=fstests@vger.kernel.org \
    --cc=jlayton@kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --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