public inbox for fstests@vger.kernel.org
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <djwong@kernel.org>
To: Jeff Layton <jlayton@kernel.org>
Cc: Zorro Lang <zlang@redhat.com>,
	fstests@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	Christian Brauner <brauner@kernel.org>
Subject: Re: [PATCH fstests v3 3/3] generic: add tests for file delegations
Date: Tue, 16 Dec 2025 09:13:33 -0800	[thread overview]
Message-ID: <20251216171333.GG7716@frogsfrogsfrogs> (raw)
In-Reply-To: <be8dace96aa68c59330f6c7be6ec5e2482bb6ca3.camel@kernel.org>

On Sun, Dec 07, 2025 at 03:35:29AM +0900, Jeff Layton wrote:
> On Sat, 2025-12-06 at 01:25 +0800, Zorro Lang 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.
> > > 
> > > Signed-off-by: Jeff Layton <jlayton@kernel.org>
> > > ---
> > 
> > This version is good to me. But this test fails without the:
> > https://lore.kernel.org/linux-fsdevel/20251201-dir-deleg-ro-v1-1-2e32cf2df9b7@kernel.org/
> > 
> 
> 
> Thanks. Yes, that bug is unfortunate. I'm hoping Christian will take
> that patch in soon so all of the tests will pass.
> 
> > So maybe we can mark that:
> > 
> >   _fixed_by_kernel_commit xxxxxxxxxxxx ...
> > 
> > or
> > 
> >   _wants_kernel_commit xxxxxxxxxxxx ...
> > 
> > Anyway, we can add that after the patchset get merged. I'll merge this patchset
> > at first.
> > 
> > Reviewed-by: Zorro Lang <zlang@redhat.com>
> 
> If you like. This functionality is only in v6.19-rc so far, so there is
> no released kernel that has this (yet).

Hi Jeff/Zorro,

Having rebased on 6.19-rc1, I now see that generic/787 (this test) fails
with:

 --- /run/fstests/bin/tests/generic/787.out	2025-12-09 09:18:49.076881595 -0800
 +++ /var/tmp/fstests/generic/787.out.bad	2025-12-16 07:23:40.092000000 -0800
 @@ -1,2 +1,4 @@
  QA output created by 787
 -success!
 +ls: cannot access '/mnt/dirdeleg': No such file or directory
 +Server reported failure (2)
 +(see /var/tmp/fstests/generic/787.full for details)

The 787.full file contains:

      ***** Client log *****
 10 tests run, 0 failed
      ***** Server log *****
      ***** Server failure *****
      in test 3, while Set Delegationing using offset 1, length 0 - err = 0:Success
      3:Fail Write Deleg if file is open somewhere else
      ***** Server failure *****
      in test 3, while Get Delegationing using offset 1, length 0 - err = 0:Success
      3:Fail Write Deleg if file is open somewhere else
      ***** Server failure *****
      in test 4, while Set Delegationing using offset 0, length 0 - err = 0:Success
      4:Fail Read Deleg if opened with write permissions
      ***** Server failure *****
      in test 4, while Get Delegationing using offset 0, length 0 - err = 0:Success
      4:Fail Read Deleg if opened with write permissions
 13 tests run, 2 failed
      ***** End file details *****
 Server reported failure (2)

(Apparently this test would _notrun in 6.18-rc)

Is this the failure fixed by the patch above?  If so, I'll ignore the
failure until rc2.

--D

> Jeff Layton <jlayton@kernel.org>
> 

  reply	other threads:[~2025-12-16 17:13 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 [this message]
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

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=20251216171333.GG7716@frogsfrogsfrogs \
    --to=djwong@kernel.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