Bug 648408 – Do not mix FMODE_ and O_ flags with break_lease() and may_open() [rhel-6.0.z]

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 648408 - Do not mix FMODE_ and O_ flags with break_lease() and may_open() [rhel-6.0.z]

Summary:	Do not mix FMODE_ and O_ flags with break_lease() and may_open() [rhel-6.0.z]

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat Enterprise Linux 6
Classification:	Red Hat
Component:	kernel (Show other bugs)
Sub Component:
Version:	6.0
Hardware:	All Linux

Priority	high Severity high
Target Milestone:	rc
Target Release:	---
Assigned To:	Frantisek Hrbata
QA Contact:	yanfu,wang
Docs Contact:

URL:
Whiteboard:
Keywords:	Regression, ZStream

Depends On:	642677 1020741
Blocks:
	Show dependency tree / graph

Reported:	2010-11-01 04:36 EDT by RHEL Product and Program Management
Modified:	2013-10-18 04:41 EDT (History)
CC List:	9 users (show)

See Also:
Fixed In Version:	kernel-2.6.32-71.9.1.el6
Doc Type:	Bug Fix
Doc Text:	Due to a mix-up between FMODE_ and O_ flags, an NFSv4 client could get a WRITE lock on a file that another NFSv4 client already had a READ lock on. As a result, data could be corrupted. With this update, FMODE_ and O_ flags are properly handled and getting a WRITE lock fails in the aforementioned case.
Story Points:	---
Clone Of:
Environment:
Last Closed:	2011-01-11 14:47:45 EST
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHSA-2011:0007	normal	SHIPPED_LIVE	Important: kernel security and bug fix update	2011-01-11 14:44:55 EST

Groups: None (edit)

Description RHEL Product and Program Management 2010-11-01 04:36:24 EDT

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

Comment 3 Frantisek Hrbata 2010-11-22 02:53:51 EST

in kernel-2.6.32-71.9.1.el6

Comment 5 yanfu,wang 2010-12-15 03:41:14 EST

reproduced on rhel6-rc4 got the same error as per https://bugzilla.redhat.com/show_bug.cgi?id=642677#c0
verified on kernel-2.6.32-71.13.1.el6 on i386 and x86_64, result passed.
server:
# ./delegation /mnt
Step1: Get READ DELEGATION
       Get Success:(/mnt/file)
Step2: Get a READ lock
       Get READ lock success.
            <== Let the program pending here, goto STEP2
Step3: Release the READ lock
       Release READ lock success.
Step4: Close file

client:
# ./lock /mnttest/file 
Step1: Open file with O_RDWR
       Open Success:(/mnttest/file)
Step2: Get a WRITE lock
ERROR: Get WRITE lock fail
Step4: Close file

Comment 7 errata-xmlrpc 2011-01-11 14:47:45 EST

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-2011-0007.html

Comment 8 Martin Prpič 2011-01-12 07:54:19 EST

    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:
Due to a mix-up between FMODE_ and O_ flags, an NFSv4 client could get a WRITE lock on a file that another NFSv4 client already had a READ lock on. As a result, data could be corrupted. With this update, FMODE_ and O_ flags are properly handled and getting a WRITE lock fails in the aforementioned case.

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