Bug 2230458

Summary:	NFSv4.1 client sends a zero valued file handle in a GETATTR after an OPEN compound with an unsuccessful GETATTR
Product:	Red Hat Enterprise Linux 9	Reporter:	Olga Kornieskaia <kolga>
Component:	kernel	Assignee:	NFS Team <nfs-team>
kernel sub component:	NFS	QA Contact:	Yongcheng Yang <yoyang>
Status:	NEW ---	Docs Contact:
Severity:	unspecified
Priority:	unspecified	CC:	xzhou, yieli
Version:	9.3
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

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: