From: Calum Mackay <calum.mackay@oracle.com>
To: bfields@redhat.com
Cc: linux-nfs@vger.kernel.org
Subject: [PATCH 1/2] pynfs: courtesy: use a helper function to prepare the lock op args
Date: Wed, 24 Mar 2021 01:46:29 +0000 [thread overview]
Message-ID: <20210324014630.2454-2-calum.mackay@oracle.com> (raw)
In-Reply-To: <20210324014630.2454-1-calum.mackay@oracle.com>
Cleanup.
Future tests to be added will use the same sequence to prepare the args
for the lock op, so use a helper function for that.
Signed-off-by: Calum Mackay <calum.mackay@oracle.com>
---
nfs4.1/server41tests/st_courtesy.py | 11 +++++++----
1 file changed, 7 insertions(+), 4 deletions(-)
diff --git a/nfs4.1/server41tests/st_courtesy.py b/nfs4.1/server41tests/st_courtesy.py
index 5e13dad44a01..e74d9afbca60 100644
--- a/nfs4.1/server41tests/st_courtesy.py
+++ b/nfs4.1/server41tests/st_courtesy.py
@@ -15,6 +15,12 @@ def _getleasetime(sess):
res = sess.compound([op.putrootfh(), op.getattr(1 << FATTR4_LEASE_TIME)])
return res.resarray[-1].obj_attributes[FATTR4_LEASE_TIME]
+def cour_lockargs(fh, stateid):
+ open_to_lock_owner = open_to_lock_owner4( 0, stateid, 0, lock_owner4(0, b"lock1"))
+ lock_owner = locker4(open_owner=open_to_lock_owner, new_lock_owner=True)
+ lock_ops = [ op.lock(WRITE_LT, False, 0, NFS4_UINT64_MAX, lock_owner) ]
+ return [op.putfh(fh)] + lock_ops
+
def testLockSleepLockU(t, env):
"""test server courtesy by having LOCK and LOCKU
in separate compounds, separated by a sleep of twice the lease period
@@ -29,10 +35,7 @@ def testLockSleepLockU(t, env):
fh = res.resarray[-1].object
stateid = res.resarray[-2].stateid
- open_to_lock_owner = open_to_lock_owner4( 0, stateid, 0, lock_owner4(0, b"lock1"))
- lock_owner = locker4(open_owner=open_to_lock_owner, new_lock_owner=True)
- lock_ops = [ op.lock(WRITE_LT, False, 0, NFS4_UINT64_MAX, lock_owner) ]
- res = sess1.compound([op.putfh(fh)] + lock_ops)
+ res = sess1.compound(cour_lockargs(fh, stateid))
check(res, NFS4_OK)
lease_time = _getleasetime(sess1)
--
2.27.0
next prev parent reply other threads:[~2021-03-24 1:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-24 1:46 [PATCH 0/2] add another courteous server test Calum Mackay
2021-03-24 1:46 ` Calum Mackay [this message]
2021-03-24 1:46 ` [PATCH 2/2] pynfs: courtesy: add a test to ensure server releases state appropriately Calum Mackay
2021-03-25 17:25 ` [PATCH 0/2] add another courteous server test J. Bruce Fields
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=20210324014630.2454-2-calum.mackay@oracle.com \
--to=calum.mackay@oracle.com \
--cc=bfields@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.