aboutsummaryrefslogtreecommitdiffstatshomepage
path: root/scripts/lib/kdoc/kdoc_output.py
diff options
context:
space:
mode:
authorChuck Lever <chuck.lever@oracle.com>2025-05-07 10:45:15 -0400
committerChuck Lever <chuck.lever@oracle.com>2025-05-11 19:48:29 -0400
commitd6ca7d2643eebe09cf46840bdc7d68b6e07aba77 (patch)
tree6911a9c83ca55b21c036605df0d4062fd6e5df0c /scripts/lib/kdoc/kdoc_output.py
parentnfsd: use SHA-256 library API instead of crypto_shash API (diff)
downloadwireguard-linux-d6ca7d2643eebe09cf46840bdc7d68b6e07aba77.tar.xz
wireguard-linux-d6ca7d2643eebe09cf46840bdc7d68b6e07aba77.zip
NFSD: Implement FATTR4_CLONE_BLKSIZE attribute
RFC 7862 states that if an NFS server implements a CLONE operation, it MUST also implement FATTR4_CLONE_BLKSIZE. NFSD implements CLONE, but does not implement FATTR4_CLONE_BLKSIZE. Note that in Section 12.2, RFC 7862 claims that FATTR4_CLONE_BLKSIZE is RECOMMENDED, not REQUIRED. Likely this is because a minor version is not permitted to add a REQUIRED attribute. Confusing. We assume this attribute reports a block size as a count of bytes, as RFC 7862 does not specify a unit. Reported-by: Roland Mainz <roland.mainz@nrubsig.org> Suggested-by: Christoph Hellwig <hch@infradead.org> Reviewed-by: Roland Mainz <roland.mainz@nrubsig.org> Cc: stable@vger.kernel.org # v6.7+ Reviewed-by: Jeff Layton <jlayton@kernel.org> Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
Diffstat (limited to 'scripts/lib/kdoc/kdoc_output.py')
0 files changed, 0 insertions, 0 deletions