diff options
| author | Chuck Lever <chuck.lever@oracle.com> | 2025-11-17 11:00:50 -0500 |
|---|---|---|
| committer | Chuck Lever <chuck.lever@oracle.com> | 2025-12-18 11:18:39 -0500 |
| commit | ad3cbbb0c1892c48919727fcb8dec5965da8bacb (patch) | |
| tree | 1ddcb43155f11cbc451c243499b5b7848fe671ad /tools/testing/selftests/sigaltstack/current_stack_pointer.h | |
| parent | 27d17641cacfedd816789b75d342430f6b912bd2 (diff) | |
NFSD: Clear TIME_DELEG in the suppattr_exclcreat bitmap
>From RFC 8881:
5.8.1.14. Attribute 75: suppattr_exclcreat
> The bit vector that would set all REQUIRED and RECOMMENDED
> attributes that are supported by the EXCLUSIVE4_1 method of file
> creation via the OPEN operation. The scope of this attribute
> applies to all objects with a matching fsid.
There's nothing in RFC 8881 that states that suppattr_exclcreat is
or is not allowed to contain bits for attributes that are clear in
the reported supported_attrs bitmask. But it doesn't make sense for
an NFS server to indicate that it /doesn't/ implement an attribute,
but then also indicate that clients /are/ allowed to set that
attribute using OPEN(create) with EXCLUSIVE4_1.
The FATTR4_WORD2_TIME_DELEG attributes are also not to be allowed
for OPEN(create) with EXCLUSIVE4_1. It doesn't make sense to set
a delegated timestamp on a new file.
Fixes: 7e13f4f8d27d ("nfsd: handle delegated timestamps in SETATTR")
Cc: stable@vger.kernel.org
Reviewed-by: Jeff Layton <jlayton@kernel.org>
Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
Diffstat (limited to 'tools/testing/selftests/sigaltstack/current_stack_pointer.h')
0 files changed, 0 insertions, 0 deletions
