From: Calum Mackay <calum.mackay@oracle.com>
To: Chen Hanxiao <chenhx.fnst@fujitsu.com>
Cc: Calum Mackay <calum.mackay@oracle.com>, linux-nfs@vger.kernel.org
Subject: Re: [PATCH] pynfs: fix key error if FATTR4_OPEN_ARGUMENTS is not supported
Date: Tue, 25 Mar 2025 20:21:14 +0000 [thread overview]
Message-ID: <2dcce01a-dc4b-4e0c-b652-dee46eddb209@oracle.com> (raw)
In-Reply-To: <20250319032402.1789-1-chenhx.fnst@fujitsu.com>
On 19/03/2025 3:23 am, Chen Hanxiao wrote:
> If FATTR4_OPEN_ARGUMENTS is not supportd, DELEG24 and DELEG25
> will throw:
> KeyError: 86
>
> Check FATTR4_OPEN_ARGUMENTS in caps from server
That's great, thanks very much.
Applied; tagged pynfs-0.3
cheers,
calum.
>
> Signed-off-by: Chen Hanxiao <chenhx.fnst@fujitsu.com>
> ---
> nfs4.1/server41tests/st_delegation.py | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/nfs4.1/server41tests/st_delegation.py b/nfs4.1/server41tests/st_delegation.py
> index fa9b451..f27e852 100644
> --- a/nfs4.1/server41tests/st_delegation.py
> +++ b/nfs4.1/server41tests/st_delegation.py
> @@ -311,6 +311,9 @@ def _testCbGetattr(t, env, change=0, size=0):
> OPEN4_SHARE_ACCESS_WRITE |
> OPEN4_SHARE_ACCESS_WANT_WRITE_DELEG)
>
> + if FATTR4_OPEN_ARGUMENTS not in caps:
> + fail("FATTR4_OPEN_ARGUMENTS not supported")
> +
> if caps[FATTR4_SUPPORTED_ATTRS] & FATTR4_OPEN_ARGUMENTS:
> if caps[FATTR4_OPEN_ARGUMENTS].oa_share_access_want & OPEN_ARGS_SHARE_ACCESS_WANT_DELEG_TIMESTAMPS:
> openmask |= 1<<OPEN_ARGS_SHARE_ACCESS_WANT_DELEG_TIMESTAMPS
prev parent reply other threads:[~2025-03-25 20:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-19 3:23 [PATCH] pynfs: fix key error if FATTR4_OPEN_ARGUMENTS is not supported Chen Hanxiao
2025-03-20 11:00 ` Jeff Layton
2025-03-25 20:21 ` Calum Mackay [this message]
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=2dcce01a-dc4b-4e0c-b652-dee46eddb209@oracle.com \
--to=calum.mackay@oracle.com \
--cc=chenhx.fnst@fujitsu.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