From: Scott Mayhew <smayhew@redhat.com>
To: calum.mackay@oracle.com
Cc: linux-nfs@vger.kernel.org
Subject: [PATCH 0/5] pynfs: a handful of fixes and a new CB_GETATTR test
Date: Fri, 3 Apr 2026 09:27:33 -0400 [thread overview]
Message-ID: <20260403132738.1482011-1-smayhew@redhat.com> (raw)
Patches 1-4 are fixes/cleanups, but patch 3 might need a change (I
removed the erroneous check, but we might want to replace it with
something else).
Patch 5 simulates an actual application issue where the application is
failing because it's getting a unexpected/surprise mtime update for a
file that it's tracking.
Scott Mayhew (5):
pynfs: ensure tests clean up after themselves
pynfs: fix the check for delegated attribute support
pynfs: remove erroneous test from DELEG24 and DELEG25
pynfs: _testCbGetattr() should check the delegation that was received
pynfs: add delegation test for CB_GETATTR after sync WRITE
nfs4.1/server41tests/st_courtesy.py | 2 +
nfs4.1/server41tests/st_delegation.py | 227 +++++++++++++++++++++++---
nfs4.1/server41tests/st_sparse.py | 10 +-
3 files changed, 215 insertions(+), 24 deletions(-)
--
2.53.0
next reply other threads:[~2026-04-03 13:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-03 13:27 Scott Mayhew [this message]
2026-04-03 13:27 ` [PATCH 1/5] pynfs: ensure tests clean up after themselves Scott Mayhew
2026-04-03 13:27 ` [PATCH 2/5] pynfs: fix the check for delegated attribute support Scott Mayhew
2026-04-03 13:27 ` [PATCH 3/5] pynfs: remove erroneous test from DELEG24 and DELEG25 Scott Mayhew
2026-04-03 14:07 ` Jeff Layton
2026-04-03 13:27 ` [PATCH 4/5] pynfs: _testCbGetattr() should check the delegation that was received Scott Mayhew
2026-04-03 13:27 ` [PATCH 5/5] pynfs: add delegation test for CB_GETATTR after sync WRITE Scott Mayhew
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=20260403132738.1482011-1-smayhew@redhat.com \
--to=smayhew@redhat.com \
--cc=calum.mackay@oracle.com \
--cc=linux-nfs@vger.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