public inbox for fstests@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Layton <jlayton@kernel.org>
To: Christoph Hellwig <hch@infradead.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: Wed, 07 Jan 2026 08:03:15 -0500	[thread overview]
Message-ID: <748ad0ea534ea14e4401a0a94d29e64f27629095.camel@kernel.org> (raw)
In-Reply-To: <aV316LhsVSl0n9-E@infradead.org>

On Tue, 2026-01-06 at 21:58 -0800, Christoph Hellwig wrote:
> On Tue, Jan 06, 2026 at 06:09:24AM -0500, Jeff Layton wrote:
> > On Mon, 2026-01-05 at 22:28 -0800, Christoph Hellwig wrote:
> > > 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.
> > 
> > There is a patch that is not yet merged:
> 
> Thanks.  Also what is the story with generic/786 on NFS?
> 
> It seems to constantly fail for me:
> 
> generic/786  5s ... [   17.862569] run fstests generic/786 at 2026-01-07 05:29:40
> [failed, exit status 1]- output mismatch (see /root/xfstests-dev/results//generic/786.out.bad)
>     --- tests/generic/786.out	2025-12-18 06:25:33.420000000 +0000
>     +++ /root/xfstests-dev/results//generic/786.out.bad	2026-01-07 05:29:47.576897353 +0000
>     @@ -1,2 +1,3 @@
>      QA output created by 786
>     -success!
>     +Server reported failure (1)
>     +(see /root/xfstests-dev/results//generic/786.full for details)
>     ...
>     (Run 'diff -u /root/xfstests-dev/tests/generic/786.out /root/xfstests-dev/results//generic/786.out.bad'  to see the entire diff)

Mea culpa.

I missed the fact that directories have a different set of
file_operations on NFS here, and those don't have the ->setlease method
set. It's a simple fix, but it looks like I'll need to do this in some
other filesystems too. I'll send a follow-on series soon.

Thanks,
-- 
Jeff Layton <jlayton@kernel.org>

      reply	other threads:[~2026-01-07 13:03 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
2026-01-06 11:09     ` Jeff Layton
2026-01-07  5:58       ` Christoph Hellwig
2026-01-07 13:03         ` Jeff Layton [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=748ad0ea534ea14e4401a0a94d29e64f27629095.camel@kernel.org \
    --to=jlayton@kernel.org \
    --cc=brauner@kernel.org \
    --cc=fstests@vger.kernel.org \
    --cc=hch@infradead.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