------- Comment From <email address hidden> 2024-04-10 11:16 EDT-------
bisected it to commit fce7913b13d0 ("NFSD: Use a bitmask loop to encode FATTR4 results")
Looks like an unfixed endianness issue since v6.7.
NFSD: Use a bitmask loop to encode FATTR4 results
The fattr4 encoder is now structured like the COMPOUND op encoder:
one function for each individual attribute, called by bit number.
Benefits include:
- The individual attributes are now guaranteed to be encoded in
bitmask order into the send buffer
- There can be no unwanted side effects between attribute encoders
- The code now clearly documents which attributes are /not/
implemented on this server
Reviewed-by: Jeff Layton <email address hidden>
Signed-off-by: Chuck Lever <email address hidden>
------- Comment From <email address hidden> 2024-04-10 11:16 EDT-------
bisected it to commit fce7913b13d0 ("NFSD: Use a bitmask loop to encode FATTR4 results")
Looks like an unfixed endianness issue since v6.7.
commit fce7913b13d0270 bcf926f986b7ef3 29e2e56eec
Author: Chuck Lever <email address hidden>
Date: Mon Sep 18 10:02:12 2023 -0400
NFSD: Use a bitmask loop to encode FATTR4 results
The fattr4 encoder is now structured like the COMPOUND op encoder:
one function for each individual attribute, called by bit number.
Benefits include:
- The individual attributes are now guaranteed to be encoded in
bitmask order into the send buffer
- There can be no unwanted side effects between attribute encoders
- The code now clearly documents which attributes are /not/
implemented on this server
Reviewed-by: Jeff Layton <email address hidden>
Signed-off-by: Chuck Lever <email address hidden>