RFC Errata


Errata Search
 
Source of RFC  
Summary Table Full Records

Found 4 records.

Status: Verified (1)

RFC 8276, "File System Extended Attributes in NFSv4", December 2017

Source of RFC: nfsv4 (wit)

Errata ID: 7050
Status: Verified
Type: Editorial
Publication Format(s) : TEXT
Reported By: Anton Rang
Date Reported: 2022-07-26
Verifier Name: RFC Editor
Date Verified: 2022-07-26

Section 1 says: 

   This document discusses (in Section 5) the reasons that NFSv4-named
   attributes, as currently standardized in [RFC5661], are unsuitable
   for representing xattrs.  Instead, it describes a separate protocol

It should say:

   This document discusses (in Section 6) the reasons that NFSv4-named
   attributes, as currently standardized in [RFC5661], are unsuitable
   for representing xattrs.  Instead, it describes a separate protocol

Notes:

The reference to the discussion of named attributes has the wrong section number.

Status: Reported (3)

RFC 8276, "File System Extended Attributes in NFSv4", December 2017

Source of RFC: nfsv4 (wit)

Errata ID: 7007
Status: Reported
Type: Technical
Publication Format(s) : TEXT
Reported By: Yuri Radchenko
Date Reported: 2022-06-27

Section 8.4.5 says: 

   | LISTXATTRS  | NFS4ERR_ACCESS, NFS4ERR_DEADSESSION, NFS4ERR_DELAY, |
   |             | NFS4ERR_INVAL, NFS4ERR_IO, NFS4ERR_MOVED,           |
   |             | NFS4ERR_NAMETOOLONG, NFS4ERR_NOFILEHANDLE,          |
   |             | NFS4ERR_NOTSUPP, NFS4ERR_NOXATTR,                   |
   |             | NFS4ERR_OP_NOT_IN_SESSION, NFS4ERR_PERM,            |
   |             | NFS4ERR_REP_TOO_BIG, NFS4ERR_REP_TOO_BIG_TO_CACHE,  |
   |             | NFS4ERR_REQ_TOO_BIG, NFS4ERR_RETRY_UNCACHED_REP,    |
   |             | NFS4ERR_SERVERFAULT, NFS4ERR_STALE,                 |
   |             | NFS4ERR_TOO_MANY_OPS, NFS4ERR_WRONG_TYPE            |

It should say:

   | LISTXATTRS  | NFS4ERR_ACCESS, NFS4ERR_DEADSESSION, NFS4ERR_DELAY, |
   |             | NFS4ERR_INVAL, NFS4ERR_IO, NFS4ERR_MOVED,           |
   |             | NFS4ERR_NAMETOOLONG, NFS4ERR_NOFILEHANDLE,          |
   |             | NFS4ERR_NOTSUPP, NFS4ERR_NOXATTR,                   |
   |             | NFS4ERR_OP_NOT_IN_SESSION, NFS4ERR_PERM,            |
   |             | NFS4ERR_REP_TOO_BIG, NFS4ERR_REP_TOO_BIG_TO_CACHE,  |
   |             | NFS4ERR_REQ_TOO_BIG, NFS4ERR_RETRY_UNCACHED_REP,    |
   |             | NFS4ERR_SERVERFAULT, NFS4ERR_STALE,                 |
   |             | NFS4ERR_TOO_MANY_OPS, NFS4ERR_WRONG_TYPE,           |
   |             | NFS4ERR_BAD_COOKIE                                  |

Notes:

rfc says
"The handling of a cookie is similar to that of the READDIR operation."
(8.4.3.4.)

It would be useful to include NFS4ERR_BAD_COOKIE status code into the list of LISTXATTRS statuses, 8.4.5. Valid Errors.

NFS for Linux included this status code.
see https://bugzilla.redhat.com/show_bug.cgi?id=2101371

Errata ID: 5195
Status: Reported
Type: Editorial
Publication Format(s) : TEXT
Reported By: Mantas Mikulenas
Date Reported: 2017-12-05

Section 3 says: 

   Baloo, the file indexing and search framework for Key Distribution
   Exchange (KDE), has moved to storing metadata such as tags, ratings,
   and comments in file system xattrs instead of a custom database for
   simplicity.  Starting with KDE Plasma 5.1, NFS is no longer supported
   due to its lack of xattr support [KDE].

It should say:

   Baloo, the file indexing and search framework for K Desktop
   Environment (KDE), has moved to storing metadata such as tags,
   ratings, and comments in file system xattrs instead of a custom
   database for simplicity.  Starting with KDE Plasma 5.1, NFS is no
   longer supported due to its lack of xattr support [KDE].

Errata ID: 7004
Status: Reported
Type: Editorial
Publication Format(s) : TEXT
Reported By: Yuri Radchenko
Date Reported: 2022-06-23

Section 8.4.5 says: 

   | LISTXATTRS  | NFS4ERR_ACCESS, NFS4ERR_DEADSESSION, NFS4ERR_DELAY, |
   |             | NFS4ERR_INVAL, NFS4ERR_IO, NFS4ERR_MOVED,           |
   |             | NFS4ERR_NAMETOOLONG, NFS4ERR_NOFILEHANDLE,          |
   |             | NFS4ERR_NOTSUPP, NFS4ERR_NOXATTR,                   |
   |             | NFS4ERR_OP_NOT_IN_SESSION, NFS4ERR_PERM,            |
   |             | NFS4ERR_REP_TOO_BIG, NFS4ERR_REP_TOO_BIG_TO_CACHE,  |
   |             | NFS4ERR_REQ_TOO_BIG, NFS4ERR_RETRY_UNCACHED_REP,    |
   |             | NFS4ERR_SERVERFAULT, NFS4ERR_STALE,

It should say:

   | LISTXATTRS  | NFS4ERR_ACCESS, NFS4ERR_DEADSESSION, NFS4ERR_DELAY, |
   |             | NFS4ERR_INVAL, NFS4ERR_IO, NFS4ERR_MOVED,           |
   |             | NFS4ERR_NAMETOOLONG, NFS4ERR_NOFILEHANDLE,          |
   |             | NFS4ERR_NOTSUPP, NFS4ERR_NOXATTR,                   |
   |             | NFS4ERR_OP_NOT_IN_SESSION, NFS4ERR_PERM,            |
   |             | NFS4ERR_REP_TOO_BIG, NFS4ERR_REP_TOO_BIG_TO_CACHE,  |
   |             | NFS4ERR_REQ_TOO_BIG, NFS4ERR_RETRY_UNCACHED_REP,    |
   |             | NFS4ERR_SERVERFAULT, NFS4ERR_STALE, NFS4ERR_TOOSMALL

Notes:

Section 8.4.3.3. DESCRIPTION says about NFS4ERR_TOOSMALL status code:

"If the server is unable
to return a single xattr name within the maxcount limit, the error
NFS4ERR_TOOSMALL will be returned to the client."

But this status code not specified in section 8.4.5. Valid Errors for LISTXATTRS operation.

Report New Errata



Advanced Search