[nfsv4] [Technical Errata Reported] RFC8881 (8022)

RFC Errata System <rfc-editor@rfc-editor.org> Mon, 08 July 2024 12:31 UTC

To: dnoveck@netapp.com, chuck.lever@oracle.com, nfsv4-ads@ietf.org, beepee@gmail.com, inacio@cert.org
From: RFC Errata System <rfc-editor@rfc-editor.org>
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20240708123154.415CE7FA79@rfcpa.rfc-editor.org>
Date: Mon, 08 Jul 2024 05:31:54 -0700
Message-ID-Hash: XQGESKPHCZOVFODR6YVILVZDWQZMV7TC
CC: ed@nuxi.nl, nfsv4@ietf.org, rfc-editor@rfc-editor.org
Precedence: list
Subject: [nfsv4] [Technical Errata Reported] RFC8881 (8022)
Archived-At: <https://mailarchive.ietf.org/arch/msg/nfsv4/2J5lyDWE7v8qjpQRb0o2yNP3Ves>

The following errata report has been submitted for RFC8881,
"Network File System (NFS) Version 4 Minor Version 1 Protocol".

--------------------------------------
You may review the report below and at:
https://www.rfc-editor.org/errata/eid8022

--------------------------------------
Type: Technical
Reported by: Ed Schouten <ed@nuxi.nl>

Section: 8.2.2

Original Text
-------------
In making comparisons between seqids, both by the client in
determining the order of operations and by the server in determining
whether the NFS4ERR_OLD_STATEID is to be returned, the possibility of
the seqid being swapped around past the NFS4_UINT32_MAX value needs
to be taken into account. When two seqid values are being compared,
the total count of slots for all sessions associated with the current
client is used to do this. When one seqid value is less than this
total slot count and another seqid value is greater than
NFS4_UINT32_MAX minus the total slot count, the former is to be
treated as lower than the latter, despite the fact that it is
numerically greater.

Corrected Text
--------------
Whatever was stated in RFC 7530 (NFSv4.0), section 9.1.3.

Notes
-----
The number of slots has no relationship with the maximum drift a seqid value may have:

- A single COMPOUND request could contain many operations that cause the seqid to change. For example, one could craft a single COMPOUND request with many of no-op OPEN_DOWNGRADEs that each increment the seqid.

- Imagine a session with two slots. One slot is used in a tight loop to repeatedly invoke OPEN on many different paths, which unbeknownst to the client all refer to the same (hardlinked) file. If the other slot is used to call CLOSE against the same file, it is not unlikely that the difference between the seqid becomes larger than two.

Instructions:
-------------
This erratum is currently posted as "Reported". (If it is spam, it
will be removed shortly by the RFC Production Center.) Please
use "Reply All" to discuss whether it should be verified or
rejected. When a decision is reached, the verifying party
will log in to change the status and edit the report, if necessary.

--------------------------------------
RFC8881 (draft-ietf-nfsv4-rfc5661sesqui-msns-04)
--------------------------------------
Title : Network File System (NFS) Version 4 Minor Version 1 Protocol
Publication Date : August 2020
Author(s) : D. Noveck, Ed., C. Lever
Category : PROPOSED STANDARD
Source : Network File System Version 4
Stream : IETF
Verifying Party : IESG

[nfsv4] [Technical Errata Reported] RFC8881 (8022) RFC Errata System