Bug 2230458 - NFSv4.1 client sends a zero valued file handle in a GETATTR after an OPEN compound with an unsuccessful GETATTR
Summary: NFSv4.1 client sends a zero valued file handle in a GETATTR after an OPEN com...
Keywords:
Status: NEW
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: kernel
Version: 9.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: NFS Team
QA Contact: Yongcheng Yang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-08-09 13:44 UTC by Olga Kornieskaia
Modified: 2023-08-10 03:32 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-165102 0 None None None 2023-08-09 13:45:56 UTC

Description Olga Kornieskaia 2023-08-09 13:44:19 UTC 
Description of problem:

NFSv4.1 client incorrectly sends a zero valued file handle in a GETATTR when it previously received an error (ERR_DELAY) on a GETATTR operation in an OPEN compound which used a CLAIM_FH type.

An upstream commit fixes that issue: "NFSv4.1: fix zero value filehandle in post open getattr". Once I'll have a commit id I'll update.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Note You need to log in before you can comment on or make changes to this bug.