Bug 120907

Summary: umount passes randmon flags to sys_umount in kernel
Product: Red Hat Enterprise Linux 2.1 Reporter: Nicholas Henke <nic>
Component: glibcAssignee: Jakub Jelinek <jakub>
Status: CLOSED ERRATA QA Contact: Brian Brock <bbrock>
Severity: high Docs Contact:
Priority: medium    
Version: 2.1CC: dhoward, fweimer
Target Milestone: ---   
Target Release: ---   
Hardware: ia64   
OS: Linux   
URL: http://lists.debian.org/debian-glibc/2003/debian-glibc-200307/msg00078.html
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2004-08-04 21:34:50 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:    
Bug Blocks: 116726    
Attachments:
Description Flags
A more correct patch for this version of glibc none

Description Nicholas Henke 2004-04-15 04:15:00 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030630

Description of problem:
Umount is called in the kernel with randon flags -- this can cause
&MNT_FORCE to be true when umount was not called with '-f'

See the URL for the complete bug description and patch -- but the
basic information is quoted here:

The problem:  On IA64, the implementation of umount(2) in glibc
and of sys_umount in the kernel results in the kernel performing
umounts with essentially random flag words.

There is a patch in the URL that fixes the problem.

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

How reproducible:
Always

Steps to Reproduce:
Reproducing this for me is seen in Lustre, trying to do a simple mount
and unmount of the file system. Since unmount things MNT_FORCE is set,
umount_begin() is called when not necessary.
    

Additional info:

I am not sure what more can be offered besides the patch.

Comment 1 Nicholas Henke 2004-04-15 04:50:14 UTC
Created attachment 99438 [details]
A more correct patch for this version of glibc

Comment 2 Jakub Jelinek 2004-04-15 07:10:40 UTC
In what way is this patch more correct than the one in CVS?
I will add the INLINE_SYSCALL version.

Comment 3 Jakub Jelinek 2004-05-25 16:14:54 UTC
ftp://people.redhat.com/jakub/glibc/errata/2.2.4-32.16/ should have
this fixed.

Comment 4 Jason Baron 2004-05-28 17:55:33 UTC
*** Bug 122505 has been marked as a duplicate of this bug. ***

Comment 5 Mark J. Cox 2004-08-04 21:34:50 UTC
An errata 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 the 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-2004-383.html