[nfsv4] [Technical Errata Reported] RFC8881 (8021)
RFC Errata System <rfc-editor@rfc-editor.org> Mon, 08 July 2024 11:03 UTC
Return-Path: <wwwrun@rfcpa.rfc-editor.org>
X-Original-To: nfsv4@ietf.org
Delivered-To: nfsv4@ietfa.amsl.com
Received: from rfcpa.rfc-editor.org (unknown [167.172.21.234]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9204FC1E0D98; Mon, 8 Jul 2024 04:03:23 -0700 (PDT)
Received: by rfcpa.rfc-editor.org (Postfix, from userid 461) id E8D7C7FA79; Mon, 8 Jul 2024 04:03:22 -0700 (PDT)
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: <20240708110322.E8D7C7FA79@rfcpa.rfc-editor.org>
Date: Mon, 08 Jul 2024 04:03:22 -0700
Message-ID-Hash: RTITXHDDH4OH7SFZN3KR5DWLJTF3ZLZ7
X-Message-ID-Hash: RTITXHDDH4OH7SFZN3KR5DWLJTF3ZLZ7
X-MailFrom: wwwrun@rfcpa.rfc-editor.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-nfsv4.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: ed@nuxi.nl, nfsv4@ietf.org, rfc-editor@rfc-editor.org
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [nfsv4] [Technical Errata Reported] RFC8881 (8021)
List-Id: NFSv4 Working Group <nfsv4.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/nfsv4/gy8tPeE9IihU0a_I4JW8aXtebDI>
List-Archive: <https://mailarchive.ietf.org/arch/browse/nfsv4>
List-Help: <mailto:nfsv4-request@ietf.org?subject=help>
List-Owner: <mailto:nfsv4-owner@ietf.org>
List-Post: <mailto:nfsv4@ietf.org>
List-Subscribe: <mailto:nfsv4-join@ietf.org>
List-Unsubscribe: <mailto:nfsv4-leave@ietf.org>
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/eid8021 -------------------------------------- Type: Technical Reported by: Ed Schouten <ed@nuxi.nl> Section: 8.2.3 Original Text ------------- In the case of an OPEN, the stateid returned for the open file and not the delegation is used. Corrected Text -------------- In the case of an OPEN, the stateid returned for the open file and not the delegation is used, with seqid set to 1 explicitly. Notes ----- There is no guarantee that OPEN always returns an open_stateid with seqid == 1. If the same file already happens to be opened, the file could get upgraded. This means that if the same COMPOUND procedure contains a CLOSE that uses the current stateid (as demonstated in Figure 4), it could end up closing a file unintentionally. The best course of action would be to require that OPEN always sets the current stateid to one having seqid == 1. That way any attempt to call CLOSE will end up returning NFS4ERR_OLD_STATEID if it turned out the OPEN did an upgrade. 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 (8021) RFC Errata System