From: Jeff Layton <jlayton@kernel.org>
To: Tigran Mkrtchyan <tigran.mkrtchyan@desy.de>, calum.mackay@oracle.com
Cc: linux-nfs@vger.kernel.org
Subject: Re: [PATCH] deleg: break infinite loop in DELEG8 test
Date: Tue, 15 Apr 2025 10:10:11 -0400 [thread overview]
Message-ID: <5fb69477dfb9e372e70caf6d320170f6a20927af.camel@kernel.org> (raw)
In-Reply-To: <20250415114814.285400-1-tigran.mkrtchyan@desy.de>
On Tue, 2025-04-15 at 13:48 +0200, Tigran Mkrtchyan wrote:
> The test assumes that the server can return either OK or DELAY,
> however, the 'break' condition checks only for OK.
>
> Signed-off-by: Tigran Mkrtchyan <tigran.mkrtchyan@desy.de>
> ---
> nfs4.1/server41tests/st_delegation.py | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/nfs4.1/server41tests/st_delegation.py b/nfs4.1/server41tests/st_delegation.py
> index ea4c073..60b0de6 100644
> --- a/nfs4.1/server41tests/st_delegation.py
> +++ b/nfs4.1/server41tests/st_delegation.py
> @@ -181,8 +181,8 @@ def testDelegRevocation(t, env):
> owner, how, claim)
> while 1:
> res = sess2.compound(env.home + [open_op])
> - if res.status == NFS4_OK:
> - break;
> + if res.status == NFS4_OK or res.status == NFS4ERR_DELAY:
> + break
> check(res, [NFS4_OK, NFS4ERR_DELAY])
> # just to keep sess1 renewed. This is a bit fragile, as we
> # depend on the above compound waiting no longer than the
Don't you want to loop on NFS4ERR_DELAY?
It looks like this is supposed to loop (with no DELEGRETURN) until the
open returns NFS4_OK. Presumably at that point the delegation will be
revoked and you'll get the expected errors.
--
Jeff Layton <jlayton@kernel.org>
next prev parent reply other threads:[~2025-04-15 14:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-15 11:48 [PATCH] deleg: break infinite loop in DELEG8 test Tigran Mkrtchyan
2025-04-15 14:10 ` Jeff Layton [this message]
2025-04-15 14:49 ` Mkrtchyan, Tigran
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=5fb69477dfb9e372e70caf6d320170f6a20927af.camel@kernel.org \
--to=jlayton@kernel.org \
--cc=calum.mackay@oracle.com \
--cc=linux-nfs@vger.kernel.org \
--cc=tigran.mkrtchyan@desy.de \
/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