From: Calum Mackay <calum.mackay@oracle.com>
To: linux-nfs@vger.kernel.org
Cc: Calum Mackay <calum.mackay@oracle.com>
Subject: pynfs-0.5 tagged and pushed
Date: Fri, 27 Mar 2026 02:57:31 +0000 [thread overview]
Message-ID: <33de50bc-5cca-4071-ad32-05a82da89c77@oracle.com> (raw)
I've applied most of the outstanding pynfs patches, and tagged and
pushed pynfs-0.5
There were a couple of patches with which I'm having difficulties in
testing, and I've emailed the authors.
If you have submitted a pynfs patch which doesn't appear below, and I've
not contacted you, apologies, and would you please let me know.
Thanks very much indeed.
cheers,
calum.
https://git.linux-nfs.org/?p=cdmackay/pynfs.git
Bryan Schmersal (5):
Actually reuse the slot only when the sequence op gets an
NFS4ERR_DELAY status. Before this patch, any NFS4ERR_DELAY would consume
a new slot even when the sequence op was not the culprit.
Replace references of non-existant StandardError with Exception
Use constants generated from the .x file for NFS_PROGRAM and
versions.
Add the ability to have NFS3Client connect using a secure port.
Allow max_retries and delay_time to be passed as arguments to
compound()
Chuck Lever (1):
Add some tests for unsupported fattr4 attributes
Scott Mayhew (4):
nfs4.1: make serverhelper() deal with "bytes" objects
pynfs: add an option to forcibly expire clients to the
serverhelper scripts
rudimentary CB_NOTIFY_LOCK support
4.1 server tests: add test for CB_NOTIFY_LOCK with an expired client
Tigran Mkrtchyan (2):
pynfs: add test for read with delegation stateid after close
nfs4.1: mark slot free after compound op complete
next reply other threads:[~2026-03-27 2:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-27 2:57 Calum Mackay [this message]
2026-03-27 14:47 ` pynfs-0.5 tagged and pushed Aurélien Couderc
2026-03-27 16:26 ` Aurélien Couderc
2026-03-27 19:08 ` Calum Mackay
2026-04-28 8:44 ` Aurélien Couderc
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=33de50bc-5cca-4071-ad32-05a82da89c77@oracle.com \
--to=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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).