From: "Antonio M." <quactinoids@gmail.com>
To: linux-nfs@vger.kernel.org
Subject: pynfs blocking lock test
Date: Tue, 17 Apr 2018 19:32:42 +0530 [thread overview]
Message-ID: <CAABTemTHvp+2rthSZNPgZBzfVvumy53bLuKS7wLEcuFopUpVig@mail.gmail.com> (raw)
Hi,
It looks like "testLongPoll" in st_lock.py is trying to test whether
lock is not granted to others before client lease expires.
However, I don't understand that the following part of the code where
lockowner3 is trying to grab a lock is also part of the same Client
and sends LOCK with the same ClientID.
...
if badpoll:
# Third owner tries to butt in and steal lock
res3 = c.lock_file("owner3", fh3, stateid3,
type=WRITEW_LT, lockowner="lockowner3_LOCK22")
...
So, after performing the LOCK operation (even though it was denied),
lease on client will be renewed.
And thus, lease will never expire. Only when the loop completes, LOCK
will be unlocked by the first owner.
Also, the test does not consider that if NFS server is implementing
delayed return of DENIAL for conflicting locks.
Does this test assume certain NFS server implementation ? Also, what
if the lease is anyway going to be renewed for failed operation since client id
would be matching and that is good enough to renew lease.
next reply other threads:[~2018-04-17 14:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-17 14:02 Antonio M. [this message]
2018-04-18 15:54 ` pynfs blocking lock 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=CAABTemTHvp+2rthSZNPgZBzfVvumy53bLuKS7wLEcuFopUpVig@mail.gmail.com \
--to=quactinoids@gmail.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 NNTP newsgroup(s).