public inbox for linux-nfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Layton <jlayton@kernel.org>
To: Calum Mackay <calum.mackay@oracle.com>
Cc: linux-nfs@vger.kernel.org, Jeff Layton <jlayton@kernel.org>
Subject: [PATCH pynfs v2 0/7] pynfs: add CB_GETATTR tests and tests for delegated timestamps
Date: Mon, 14 Oct 2024 16:50:20 -0400	[thread overview]
Message-ID: <20241014-cb_getattr-v2-0-3782e0d7c598@kernel.org> (raw)

I sent these a month or so ago, but Calum was on PTO. Sending again,
with some additions.

This patchset adds a couple of CB_GETATTR tests, and then updates them
to also test delegated mtime support. There is also a patch to make
the nfsv4.1 tests default to minorversion 2

Signed-off-by: Jeff Layton <jlayton@kernel.org>
---
Changes in v2:
- check timestamps in WRT18, and pass_warn if they don't change
- have v4.1 tests default to minorversion 2
- have DELEG2 open the file r/w
- add support for the "delstid" draft symbols
- test delegated timestamps in new CB_GETATTR tests
- Link to v1: https://lore.kernel.org/r/20240905-cb_getattr-v1-0-0af05c68234f@kernel.org

---
Jeff Layton (7):
      WRT18: have it also check the ctime between writes
      DELEG2: fix write delegation test to open the file RW
      pynfs: update maintainer info
      nfs4.1: add two CB_GETATTR tests
      nfs4.1: default to minorversion 2
      nfs4.1: add support for the "delstid" draft
      st_deleg: test delegated timestamps in CB_GETATTR

 CONTRIBUTING                          |   6 +-
 nfs4.0/servertests/st_write.py        |  28 ++++++---
 nfs4.1/nfs4client.py                  |   8 ++-
 nfs4.1/nfs4lib.py                     |   3 +
 nfs4.1/server41tests/environment.py   |   3 +
 nfs4.1/server41tests/st_delegation.py | 102 ++++++++++++++++++++++++++++++-
 nfs4.1/testserver.py                  |   2 +-
 nfs4.1/xdrdef/nfs4.x                  | 111 ++++++++++++++++++++++++++++++++--
 8 files changed, 242 insertions(+), 21 deletions(-)
---
base-commit: c75f65983498a3254e3970da86eb6954415cac01
change-id: 20240905-cb_getattr-8db184a5b4bf

Best regards,
-- 
Jeff Layton <jlayton@kernel.org>


             reply	other threads:[~2024-10-14 20:50 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-14 20:50 Jeff Layton [this message]
2024-10-14 20:50 ` [PATCH pynfs v2 1/7] WRT18: have it also check the ctime between writes Jeff Layton
2024-10-14 20:50 ` [PATCH pynfs v2 2/7] DELEG2: fix write delegation test to open the file RW Jeff Layton
2024-10-14 20:50 ` [PATCH pynfs v2 3/7] pynfs: update maintainer info Jeff Layton
2024-10-14 20:50 ` [PATCH pynfs v2 4/7] nfs4.1: add two CB_GETATTR tests Jeff Layton
2024-10-14 20:50 ` [PATCH pynfs v2 5/7] nfs4.1: default to minorversion 2 Jeff Layton
2024-10-15 13:43   ` Chuck Lever III
2024-10-15 14:23     ` Jeff Layton
2024-10-15 19:20       ` Chuck Lever III
2024-10-14 20:50 ` [PATCH pynfs v2 6/7] nfs4.1: add support for the "delstid" draft Jeff Layton
2024-10-14 20:50 ` [PATCH pynfs v2 7/7] st_deleg: test delegated timestamps in CB_GETATTR Jeff Layton
2024-10-14 21:24 ` [PATCH pynfs v2 0/7] pynfs: add CB_GETATTR tests and tests for delegated timestamps Calum Mackay
2024-10-22 21:56 ` Calum Mackay

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=20241014-cb_getattr-v2-0-3782e0d7c598@kernel.org \
    --to=jlayton@kernel.org \
    --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