Bug 642628

Summary:	[5.6 FEAT] NFSv4 remove does not wait for close. Silly rename [rhel-5.5.z]
Product:	Red Hat Enterprise Linux 5	Reporter:	RHEL Program Management <pm-rhel>
Component:	kernel	Assignee:	Jiri Pirko <jpirko>
Status:	CLOSED ERRATA	QA Contact:	Red Hat Kernel QE team <kernel-qe>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	5.6	CC:	bugproxy, dhoward, jburke, jjarvis, jlayton, jpirko, nobody+PNT0273897, pm-eus, rkhan, rwheeler, sbest, steved, yanwang
Target Milestone:	rc	Keywords:	FutureFeature, ZStream
Target Release:	---
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:	Previously, Connectathon test cases performed on a z/OS NFSv4 server were regularly failing. While the file was being closed prior to the unlink call, the client did not wait for the close to complete before proceeding. This caused it to perform an inappropriate rename instead of unlinking the file, even though it was not required. With this update, removals on NFSv4 mounts should wait for outstanding close calls to complete before proceeding.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2010-11-09 18:09:43 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	565974
Bug Blocks:	628889

Description RHEL Program Management 2010-10-13 13:06:46 UTC

This bug has been copied from bug #565974 and has been proposed
to be backported to 5.5 z-stream (EUS).

Comment 2 Jiri Pirko 2010-10-16 09:06:17 UTC

in kernel 2.6.18-194.21.1.el5

linux-2.6-fs-nfs-wait-for-close-before-silly-renaming.patch

Comment 6 errata-xmlrpc 2010-11-09 18:09:43 UTC

An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHSA-2010-0839.html

Comment 7 Martin Prpič 2010-11-11 13:58:59 UTC

    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
Previously, Connectathon test cases performed on a z/OS NFSv4 server were regularly failing. While the file was being closed prior to the unlink call, the client did not wait for the close to complete before proceeding. This caused it to perform an inappropriate rename instead of unlinking the file, even though it was not required. With this update, removals on NFSv4 mounts should wait for outstanding close calls to complete before proceeding.