Bug 729090 – mmapping a read only file on a gfs2 filesystem incorrectly acquires an exclusive glock

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

Bug 729090 - mmapping a read only file on a gfs2 filesystem incorrectly acquires an exclusive glock

Summary:	mmapping a read only file on a gfs2 filesystem incorrectly acquires an exclus...

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat Enterprise Linux 5
Classification:	Red Hat
Component:	kernel (Show other bugs)
Sub Component:
Version:	5.6
Hardware:	x86_64 Linux

Priority	urgent Severity high
Target Milestone:	rc
Target Release:	---
Assigned To:	Phillip Lougher
QA Contact:	Red Hat Kernel QE team
Docs Contact:

URL:
Whiteboard:
Keywords:	ZStream

Duplicates:	729088 (view as bug list)
Depends On:	672724
Blocks:
	Show dependency tree / graph

Reported:	2011-08-08 13:15 EDT by Ken Reilly
Modified:	2011-09-22 05:19 EDT (History)
CC List:	15 users (show)

See Also:
Fixed In Version:	kernel-2.6.18-238.24.1.el5
Doc Type:	Bug Fix
Doc Text:	Performance issues occurred when multiple nodes attempted to call mmap() on the same inode at the same time on a GFS2 file system, as it was using an exclusive glock. With this update, a shared lock is used when "noatime" is set on the mount, allowing mmap() operations to occur in parallel, fixing this bug. Note that this issue only refers to mmap() system calls, and not to subsequent page faults.
Story Points:	---
Clone Of:
Environment:
Last Closed:	2011-09-20 13:51:33 EDT
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:1321	normal	SHIPPED_LIVE	Moderate: kernel security and bug fix update	2011-09-20 13:50:47 EDT

Groups: None (edit)

Comment 4 Steve Whitehouse 2011-08-08 14:17:24 EDT

Can you confirm the difference between this bug and bug #729088 ?

Comment 5 Steve Whitehouse 2011-08-10 04:33:18 EDT

*** Bug 729088 has been marked as a duplicate of this bug. ***

Comment 7 Phillip Lougher 2011-08-30 12:42:07 EDT

in kernel-2.6.18-238.24.1.el5

linux-2.6-fs-gfs2-no-exclusive-glocks-on-mmapped-read-only-fs.patch

Comment 10 errata-xmlrpc 2011-09-20 13:51:33 EDT

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHSA-2011-1321.html

Comment 11 Martin Prpič 2011-09-22 05:19:04 EDT

    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:
Performance issues occurred when multiple nodes attempted to call mmap() on the same inode at the same time on a GFS2 file system, as it was using an exclusive glock. With this update, a shared lock is used when "noatime" is set on the mount, allowing mmap() operations to occur in parallel, fixing this bug. Note that this issue only refers to mmap() system calls, and not to subsequent page faults.

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